security-review-checklist
Skill0 starsChanged 5 months agoMITView on GitHub
Use when reviewing feature specs, tool integrations, agent workflows, API changes, or launch plans for security concerns such as auth, secrets, data exposure, abuse paths, and approval gates.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- listener-He/java-harness-agenttheir own version, first seen Oct 20, 2026
- CrazyElephantX/OpenCodetheir own version, first seen Aug 10, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- listener-He/java-harness-agent★ 16same name
- CrazyElephantX/OpenCode★ 2same 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 repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- architecture-rfc-reviewSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- customer-call-to-prdSkill
- database-migration-risk-reviewSkill
- dependency-upgrade-risk-reviewSkill
- incident-log-to-postmortemSkill
- messy-notes-to-decision-logSkill
- privacy-data-flow-mapSkill
- prompt-to-eval-rubricSkill
- repo-launch-readiness-reviewSkill
- roadmap-to-release-planSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 10
Create a pragmatic security review checklist for a feature or workflow.
- Distinctive: line 14
Use when a feature, tool, integration, or agent workflow can affect data, auth, secrets, or external actions.
- Distinctive: line 15
Do not use when the change is purely cosmetic and has no trust boundary or data-flow impact.
- Distinctive: line 27
Look for abuse paths, privilege escalation, data leakage, and unsafe defaults.
≈ “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.
Files
Security Review Checklist
Purpose
Create a pragmatic security review checklist for a feature or workflow.
Fit
- Use when a feature, tool, integration, or agent workflow can affect data, auth, secrets, or external actions.
- Do not use when the change is purely cosmetic and has no trust boundary or data-flow impact.
Inputs
- Feature spec, tool list, API change, workflow description, or launch plan.
- Auth model, data handled, deployment surface, and user roles if available.
- Known security requirements or compliance constraints.
Workflow
- Identify assets, actors, trust boundaries, and sensitive data.
- Review auth, authorization, secrets, logging, and external calls.
- Look for abuse paths, privilege escalation, data leakage, and unsafe defaults.
- Convert findings into checks and required approvals.
- Separate blockers from follow-up hardening.
Output
Produce Markdown with:
- Security Scope
- Assets And Trust Boundaries
- Risk Checklist
- Required Controls
- Approval Gates
- Blockers
- Follow-Up Hardening
Validation
- Sensitive data paths are explicit.
- Auth and authorization are checked separately.
- Findings have practical controls.
- Public or external writes require approval gates.
- Unknown security context is not treated as safe.
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.