Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计异常

sarif-issue-reporter萨里夫问题记者

Agent Skill

用于围绕 GitHub 仓库、Issue、Pull Request、分支、提交和代码协作流程提供辅助能力。它适合让 Agent 查询项目状态、整理变更、辅助创建或检查协作事项,并把仓库中的信息转成可执行的下一步。使用时需要区分只读查询和写入操作;涉及创建 PR、修改 Issue、推送分支或访问私有仓库时,应确认 token 权限、目标仓库范围和用户授权。

总安装

196

周安装

8

GitHub Stars

4

下载量

63
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sarif-issue-reporter(萨里夫问题记者)
来源仓库:https://github.com/igbuend/grimbard
仓库路径:skills/sarif-issue-reporter
安装命令:
npx skills add https://github.com/igbuend/grimbard --skill sarif-issue-reporter
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/igbuend/grimbard --skill sarif-issue-reporter

简介

用于围绕 GitHub 仓库、Issue、Pull Request 和代码协作流程提供辅助能力。

  • 适合查询项目状态、整理变更、辅助创建或检查协作事项,并将信息转为可执行下一步。
  • 使用时需区分只读查询与写入操作,涉及 PR、Issue 修改或私有仓库访问时确认权限与授权。
  • 安装通过 GitHub 仓库,适用于 Codex、Claude、Cursor、Gemini CLI 等宿主环境。
  • 建议核验来源 README 以了解具体用法及维护状态,避免触发未预期的文件读写或命令执行。

SKILL.md

SARIF Issue Reporter

Analyze SARIF files and generate comprehensive security reports.

Target: $ARGUMENTS (path to SARIF file)

When to Use This Skill

  • Reviewing static analysis results from security scanners
  • Generating vulnerability reports with CVSS scoring
  • Validating SAST findings (true vs false positives)
  • Mapping vulnerabilities to compliance frameworks
  • Creating remediation guidance with code examples

Core Capabilities

CapabilityDescription
SARIF ParsingRead SARIF 2.1.0 format from any scanner
VerificationConfirm findings, identify false positives
CVSS ScoringCalculate scores with vector strings
Standards MappingOWASP, CWE, CAPEC, compliance frameworks
RemediationCode examples and implementation steps

Workflow

Phase 1: Parse SARIF

  1. Load SARIF file at $ARGUMENTS
  2. Extract tool metadata from runs[].tool.driver
  3. Get all results from runs[].results[]
  4. Categorize by severity level

Phase 2: Verify Each Issue

  1. Extract: Location, snippet, codeFlows, related locations
  2. Verify: Confirm issue exists, check for false positives, assess exploitability
  3. Enhance: Request additional code context if needed

Phase 3: Security Assessment

CVSS 3.1 Scoring - Calculate and justify each metric:

  • Attack Vector (AV): N/A/L/P
  • Attack Complexity (AC): L/H
  • Privileges Required (PR): N/L/H
  • User Interaction (UI): N/R
  • Scope (S): U/C
  • Impact (C/I/A): N/L/H each

Vector format: CVSS:3.1/AV:_/AC:_/PR:_/UI:_/S:_/C:_/I:_/A:_

Impact Analysis: Technical impact, business impact, exploitability, affected assets.

Phase 4: Standards Mapping

Map each verified issue to:

StandardAction
OWASP Top 10Identify category (A01-A10)
CWESpecific ID + parent/child
CAPECAttack patterns
CompliancePCI-DSS, GDPR, SOC 2, HIPAA, ISO 27001, NIST

Reference: OWASP Top 10 | CWE | CAPEC

Phase 5: Report Generation

For each verified issue, generate this report structure:

## [ISSUE-XXX] {Title}

**Severity**: {Critical|High|Medium|Low} | **CVSS**: {Score} ({Vector}) | **Status**: Verified

### Summary
{2-3 sentence overview}

### Code Evidence
**Location**: `{file}:{line}`

{code snippet with context}


### Exploitation

**Attack Vector**: {Description} **PoC**: {Example exploit code or request} **Prerequisites**: {What attacker needs}

### Impact

- **C/I/A**: {Confidentiality/Integrity/Availability impacts}
- **Business**: {Consequences}

### Standards Mapping

- **OWASP**: {Category}
- **CWE**: CWE-{ID}
- **CAPEC**: CAPEC-{ID}
- **Compliance**: {PCI-DSS/GDPR/SOC2 requirements}

### Security Patterns Violated

- **{Pattern}**: Expected {X}, found {Y}

### Remediation

**Priority**: {Level}

{Fix code}


**Steps**: {Implementation guidance}

### Validation

{Test commands or verification steps}

Implementation Steps

  1. Load SARIF - Parse JSON at $ARGUMENTS path
  2. Extract Issues - Get runs[].results[] array
  3. For Each Issue:

- Get location from physicalLocation - Read code context if snippet missing - Verify finding exists in source - Calculate CVSS with justification - Map to standards (OWASP/CWE/CAPEC) - Generate remediation code

  1. Output Report - Markdown format (primary)

Quality Checklist

Before finalizing each issue:

  • [ ] CVSS score calculated with justification
  • [ ] Code evidence with context
  • [ ] Realistic exploitation scenario
  • [ ] Security pattern identified
  • [ ] OWASP/CWE/CAPEC mapped
  • [ ] Working remediation code

SARIF Reference: SARIF 2.1.0 Spec

Example Usage


User: Analyze results.sarif and report critical/high issues Claude:

1. Parse SARIF → 2. Filter by severity → 3. Verify each finding
2. Calculate CVSS → 5. Map to standards → 6. Generate report

Best Practices

PracticeWhy
Always verifySAST tools produce false positives
Realistic exploitationTheoretical attacks aren't useful
Working remediation codeNot pseudo-code
Complete standards mappingOWASP/CWE/CAPEC/Compliance
Sufficient code contextUnderstand the full picture

Executive Summary Template

# Security Analysis Report
**Tool**: {name} | **Date**: {date} | **Scope**: {files scanned}

## Overview
| Metric | Count |
|--------|-------|
| Total Issues | {n} |
| Verified | {n} |
| False Positives | {n} |

## Severity Distribution
Critical (9.0-10.0): {n} | High (7.0-8.9): {n} | Medium (4.0-6.9): {n} | Low (0.1-3.9): {n}

## Top Risks
1. {Issue} - CVSS {score}
2. {Issue} - CVSS {score}
3. {Issue} - CVSS {score}

Anti-Patterns

  • Reporting unverified issues
  • Generic remediation advice
  • Missing exploitation scenarios
  • Incomplete CVSS justification
  • Ignoring code context

Success Criteria

  • All critical/high issues verified
  • CVSS scores justified
  • Working exploitation examples
  • Production-ready remediation code
  • Complete standards mapping

References

Helper script available: scripts/sarif_helper.py

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.86%
按下载量换算24

Claude

29.29%
按下载量换算18

Cursor

17.89%
按下载量换算11

Gemini CLI

9.51%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

未通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills