repo-security-review
Skill32 starsChanged 25 days agoNo licenceView on GitHub
Full automated security review pipeline for a code repository. Use this skill whenever the user asks to: review a repo for security issues, run a security audit, find vulnerabilities in a codebase, perform a security assessment, check for OWASP Top 10 and OWASP API Top 10 issues, scan for secrets or exposed credentials, audit dependencies for CVEs, or analyze architecture for security flaws. Trigger even for casual phrasings like "can you check this repo for security issues" or "run security on this". This skill orchestrates a multi-phase pipeline of isolated subagents: secret scanning, tech-stack detection, architectural analysis, dependency CVE scanning with reachability validation, code-level OWASP analysis, independent finding validation (confirm / needs review / reject), and final report generation. Opt-in extras: persisted PoC scripts (`--poc`), dynamic verification against the app in Docker (`--runtime`, independent of `--poc`), a live deployment check (`--verify-deployment`), and severity calibration for local-only tools (`--local`). Also supports multi-repo system reviews (`--repos`), third-party/vendor adoption audits (`--vendor` — trigger on "is this open-source tool safe to adopt"), and reviewing a single pull request's diff for security issues (`--pr` flag) — trigger on phrasings like "review this PR for security issues" or "security review this diff before merge" — a fast, diff-scoped mode that does not require the repo to have been scanned before.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- withpiper/pipekittheir own version, first seen Nov 8, 2026
- CaseyLabs/kc-secure-repo-templatetheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- CaseyLabs/kc-secure-repo-template★ 9same name
- withpiper/pipekit★ 6same name
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.
The file
Show its rules and text
We split this skill into the rules it gives an agent
34 rules. About 0 are common, 10 are distinctive, and 24 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
24
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
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.