impact-verifier
Skill1 starsChanged 3 months agoMITView on GitHub
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- personaSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Verify: Run the specific verify workflow for the impact class.
- Distinctive: line 45
All standard evidence artifacts present.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Impact Verifier
Overview
The final gate before reporting. Converts candidate findings into confirmed bounty-grade reports only when impact is proven. Enforces evidence completeness, false-positive checks, impact classification, and report readiness scoring.
Quick Reference
- Skill: impact-verifier
- Version: 1.1.0
- Bounded Context: ImpactContext
- Required tools:
python3,jq,curl - Risk tier: passive (validates, does not test)
Workflow Selection
- Collect:
collect-candidatesfrom all skill output directories. - Classify:
classify-impactto determine impact class. - Verify: Run the specific verify workflow for the impact class.
- Gate:
false-positive-gateandreport-readinessbefore reporting. - Score:
cvss4-scorefor CVSS 4.0 severity, thenimpact-narrativefor the impact write-up.
Available Workflows
| Workflow | Purpose |
collect-candidates | Aggregate candidate findings from all skill outputs. |
classify-impact | Determine impact class for a candidate finding. |
verify-data-exposure | Prove actual data exposure from unauthorized access. |
verify-privilege-escalation | Prove role/permission boundary was broken. |
verify-account-takeover | Prove full account takeover path. |
verify-tenant-break | Prove cross-tenant data access. |
false-positive-gate | Run automated false-positive checks. |
report-readiness | Score finding readiness for submission. |
cvss4-score | Calculate CVSS 4.0 score, macrovector, and severity from a vector. |
impact-narrative | Generate impact narrative with attack scenario and PII detection. |
Workflow Selection Notes
cvss4-scoreneedsCVSS4_VECTORin context (full vector string starting withCVSS:4.0/).impact-narrativeneedsFINDING_DIR(evidence directory withresponse.txt) andIMPACT_CLASS(e.g.account_takeover,data_exposure,tenant_break,rce).- The narrative auto-detects sensitive fields (
email,token,card_number, ...) in the captured response and strengthens the evidence section accordingly.
Evidence Required
- Impact class confirmation with proof artifacts.
- False-positive checklist completed.
- Report readiness score >= 80.
- All standard evidence artifacts present.
- CVSS 4.0 vector string with metric breakdown (
cvss4.json). - Impact narrative with attack scenario and observed data classes (
impact.md). - Redact credentials, session cookies, bearer tokens, and auth headers from all collected evidence before reporting. Evidence stays local-only under
$OUTDIR/impact-verifierand is never committed; sanitize requests/responses (gitignore evidence directories) so no secrets leak into reports.
References
- Bugcrowd VRT 1.18
- FIRST CVSS v4.0 specification (macrovector bands)
- OWASP ASVS V4 (Access Control)
- OWASP Reporting guidelines
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

