agentleFS
codexstar69codexstar69/bug-hunter/skills/security-review/SKILL.md

security-review

Skill546 starsChanged 3 months agoMITView on GitHub

Run a focused STRIDE-based security review using Bug Hunter-native artifacts. Use whenever the user asks for a full security audit, repository security review, weekly security scan, PR security review with deeper validation, or wants dependency CVEs and threat-model context combined into one workflow.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for deeper security audits than a simple bug hunt, especially when the user wants:

    line 12
  2. Very specific:

    If missing, invoke the bundled threat-model-generation skill.

    line 22
  3. Distinctive:

    If dependency scanning is relevant, run:

    line 30
  4. Very specific:

    Keep all paths Bug Hunter-native.

    line 55
  5. Distinctive:

    Prefer validated, exploitability-aware findings over raw volume.

    line 56

“Common” is measured: kept by at least 6 in 10 of the 167 edited versions of this file we could read. “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

Security Review

This is a bundled local Bug Hunter companion skill. It packages a security-focused review workflow without introducing any external marketplace dependency.

Purpose

Use this skill for deeper security audits than a simple bug hunt, especially when the user wants:

  • a full security review
  • PR security validation
  • weekly security scanning
  • dependency reachability + code review together
  • threat-model-driven analysis

Workflow

  1. Ensure .bug-hunter/threat-model.md exists.
    • If missing, invoke the bundled threat-model-generation skill.
  2. Determine the scan mode from the request:
    • PR → diff-scoped review via commit-security-scan
    • staged → staged-only security review
    • weekly → recent commit range on the default branch
    • full → full repository security audit
  3. If dependency scanning is relevant, run:
    • node scripts/dep-scan.cjs --target <path> --output .bug-hunter/dep-findings.json
  4. Scan code for STRIDE threats using Bug Hunter-native conventions. Reuse:
    • .bug-hunter/triage.json
    • .bug-hunter/threat-model.md
    • .bug-hunter/security-config.json
    • .bug-hunter/dep-findings.json
  5. Validate severe findings using the bundled vulnerability-validation skill.
  6. Produce structured outputs compatible with the Bug Hunter pipeline.

Outputs

Primary artifacts should stay inside .bug-hunter/:

  • .bug-hunter/hunter-findings.json
  • .bug-hunter/referee.json
  • .bug-hunter/report.md
  • .bug-hunter/dep-findings.json when dependency review is enabled
  • .bug-hunter/fix-strategy.json if the user wants remediation planning

Important constraints

  • Keep all paths Bug Hunter-native; do not emit .factory/* artifacts.
  • Prefer validated, exploitability-aware findings over raw volume.
  • For patching requests, hand findings back to the normal Bug Hunter fix pipeline rather than inventing a second patch system.

Download now (ZIP)

  • Other versions192 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 192

    1. affaan-m/ECC★ 246ksame name
    2. github/awesome-copilot★ 41ksame name
    3. langfuse/langfuse★ 37ksame name
    4. nearai/ironclaw★ 13ksame name
    5. joe-bell/cva★ 6.9ksame name
    6. doorkeeper-gem/doorkeeper★ 5.5ksame name
    7. compozy/compozy★ 2.8ksame name
    8. getsentry/sentry-python★ 2.2ksame name
    9. trycompai/comp★ 2.1ksame name
    10. xu-xiang/everything-claude-code-zh★ 1.9ksame name

    182 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use dependency-cve-sweep, fleet-standard-adoption and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • berntpoppSkill

      dependency-cve-sweep

      Use when handling Dependabot PRs, CodeQL/Trivy alerts, or doing a routine dependency/CVE sweep for this repo.

      Also in 12 projects that use this

    • berntpoppSkill

      fleet-standard-adoption

      Use when bringing this repo into compliance with a GeneFoundry fleet standard (tool-naming, response-envelope, container-hardening, versioning, MCP transport, or logging) or closing its tracking issue.

      Also in 12 projects that use this

    • niloykumarbarmanSkill

      agent-sort

      Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

      Also in 12 projects that use this

    • ysyecustSkill

      brand-discovery

      Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).

      Also in 5 projects that use this

    • InfopibeSkill

      everything-claude-code

      Also in 11 projects that use this

    • royaluniondesign-sysSkill

      configure-ecc

      Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

      Also in 10 projects that use this

    • +2 more from berntpopp
  • In this repository12 other files it gives its agents.

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.