secreview
Skill2 starsChanged 8 months agoApache-2.0View on GitHub
Quick security review of a file, component, or change. Runs input validation audit, crypto review, dependency scan, secret detection, and access control checks.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mrveiss/AutoBot-AItheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mrveiss/AutoBot-AI★ 44same 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.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commit-push-prSkill
- freshSkill
- goSkill
- grillSkill
- investigateSkill
- prove-itSkill
- retroSkill
- saveSkill
- statusSkill
- tddSkill
- teamSkill
- techdebtSkill
- test-and-fixSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 11
Run a focused SecOps review of the current change.
- Distinctive: line 16
Input Validation Audit: Check all trust boundaries for proper sanitization
- Distinctive: line 17
Crypto Review: Verify algorithm choices, key management, certificate handling
- Distinctive: line 18
Dependency Scan: Check for known CVEs in any new or updated dependencies
- Distinctive: line 20
Access Control: Verify authorization checks are present and correct
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
/secreview — Quick Security Review
Run a focused SecOps review of the current change.
Process
As the SecOps agent, perform:
- Input Validation Audit: Check all trust boundaries for proper sanitization
- Crypto Review: Verify algorithm choices, key management, certificate handling
- Dependency Scan: Check for known CVEs in any new or updated dependencies
- Secret Detection: Scan for hardcoded credentials, keys, tokens
- Access Control: Verify authorization checks are present and correct
Target
$ARGUMENTS
Output
# Security Review: [Subject]
**Risk Level**: CRITICAL / HIGH / MEDIUM / LOW
**Blocking Issues**: [count]
## Findings
[numbered findings with severity, impact, and remediation]
## Approved / Blocked
[decision with conditions if applicable]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.

