agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/standard-catalog/SKILL.md

standard-catalog

Skill1 starsChanged 3 months agoMITView on GitHub

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start with validate to ensure catalog integrity.

    line 16
  2. Very specific:

    Run search by keyword to find standards items.

    line 17
  3. Very specific:

    Run export to generate a combined JSON for use in reports.

    line 18
  4. Distinctive:

    If a workflow has no script reference, treat it as a manual or tool-native workflow.

    line 20
  5. Distinctive:

    Not applicable — this skill produces reference data, not vulnerability findings.

    line 30
  6. Distinctive:

    All catalogs include source URLs and version information for provenance.

    line 31

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Standard Catalog

Overview

Canonical standards reference for the bug bounty toolkit. Every bug bounty test maps to an external standard (OWASP WSTG, ASVS, API Top 10, Bugcrowd VRT, CWE, PortSwigger Academy, CISA KEV, OWASP MASVS). This catalog is the single source of truth for WHAT those standards contain, enabling the coverage ledger to track WHAT we test against whom.

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

Quick Reference

  • Skill: standard-catalog
  • Severity range: info
  • Required tools: python3
  • Expected input files: none
  • Scope check: not applicable — read-only reference data.

Workflow Selection

  • Start with validate to ensure catalog integrity.
  • Run search by keyword to find standards items.
  • Run export to generate a combined JSON for use in reports.
  • Runbooks: use runbooks/.
  • If a workflow has no script reference, treat it as a manual or tool-native workflow.

Available Workflows

WorkflowPurposeScript pathsPrimary outputsEvidence
validateValidate all catalog YAML files for structure integrity..claude/skills/standard-catalog/scripts/validate_catalog.py$OUTDIR/standard-catalog/validation.json$OUTDIR/standard-catalog/evidence/
searchSearch across all catalogs by keyword..claude/skills/standard-catalog/scripts/search_standards.py$OUTDIR/standard-catalog/search_results.json$OUTDIR/standard-catalog/evidence/
exportExport a combined reference JSON with all standard IDs..claude/skills/standard-catalog/scripts/export_references.py$OUTDIR/standard-catalog/references.json$OUTDIR/standard-catalog/evidence/

Evidence Required

  • Not applicable — this skill produces reference data, not vulnerability findings.
  • All catalogs include source URLs and version information for provenance.

References

  • Source of truth: skill.yaml
  • Runbooks: runbooks/
  • OWASP WSTG: WSTG-INFO-01 through WSTG-INFO-10
  • Covered standards: WSTG Latest, ASVS 5.0, API Top 10 2023, Bugcrowd VRT 1.18, CWE Top 50, CISA KEV, PortSwigger Academy, OWASP MASVS

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.