secure-api-review
Skill4 starsChanged 30 days agoMITView on GitHub
Apply the API security standard. Use whenever you create or change an HTTP/gRPC endpoint, route, controller or handler, review API code, or write or modify an OpenAPI/proto contract.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- imsungbin/ai-native-sdlc-playbookedited, first seen Sep 3, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- imsungbin/ai-native-sdlc-playbook★ 018% same
Wrote their own version · 0
None found.
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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- brand-guidelinesSkill
- compliance-policySkill
- intent-templateSkill
- secure-api-reviewSkill
- security-policySkill
- ux-standardsSkill
- brand-guidelinesSkill
- compliance-policySkill
- intent-templateSkill
- security-policySkill
- ux-standardsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Very specific: line 12
Authentication: every route requires <the gateway token / session mechanism>.
- Distinctive: line 14
Authorization: check the caller's permission for the specific resource, not only that they are logged in.
- Very specific: line 20
Audit: every state-changing call emits an audit event with actor, action, target and time via <audit library/function>.
- Very specific: line 27
Run bash .agents/skills/secure-api-review/scripts/check-endpoints.sh and include its output in your summary.
- Distinctive: line 32
Stop and flag it as an area of concern for the policy owner.
≈ “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
Secure API standard
Owner: <security architect> · Source of truth: <link to the API security policy> · Policy version: <x.y>
Apply every rule below to each endpoint you add or change.
- Authentication: every route requires
<the gateway token / session mechanism>. The only anonymous routes are<e.g. /health, /ready>. - Authorization: check the caller's permission for the specific resource, not only that they are logged in. Deny by default.
- Input validation: validate path, query and body against the contract
(
<OpenAPI/proto location>); reject unknown fields; bound sizes and lengths. - Output: return only fields the contract declares. Errors never echo input, stack traces or internal identifiers.
- Audit: every state-changing call emits an audit event with actor, action, target and
time via
<audit library/function>. - Sensitive data: fields classified as
<pii / confidential>never appear in logs, metrics labels or error messages. - Rate limiting: public endpoints declare a limit in
<where limits are configured>.
Check
Run bash .agents/skills/secure-api-review/scripts/check-endpoints.sh and include its
output in your summary. If it reports a finding you believe is wrong, say so explicitly
instead of silencing it.
If a rule cannot be met
Stop and flag it as an area of concern for the policy owner. Do not invent an exception.
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.