api-security-review
Skill1 starsChanged 2 days agoLicence not identifiedView on GitHub
Read-only security audit of a repo's API and web app; each finding comes with path:line, trace and fix. Looks for SQL injection (queries built from strings), endpoints with no auth or no per-object authorization, endpoints, login or OTP with no rate limiting, user input that gets executed (eval, shell) or rendered unescaped (XSS), overly open CORS, badly validated JWT, OAuth or 2FA, API keys in the frontend and passwords with a fast hash. Reports, and applies only what the user picks. Use it for "audit my API security", "check for SQLi or XSS", "is my CORS config safe", "find unauthenticated endpoints", "does my login need a rate limit?", "am I storing passwords right?", or the OWASP API Top 10, even without the word "security". Not for reviewing only the pending diff (use security-review), pentesting against a server, or sizing a rate limiter (perf-diagnosis). Also triggers on Spanish requests such as "revisa la seguridad de mi API", "busca SQL injection", "¿hay endpoints sin auth?" or "¿mi CORS está bien?".
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Viprasol-Tech/api-security-reviewtheir own version, first seen Jun 13, 2026
- DigitalExplorers/agent-skillstheir own version, first seen Apr 29, 2026
- thomast1906/github-copilot-agent-skillstheir own version, first seen Apr 22, 2026
- apisec-inc/apisec-skillstheir own version, first seen Mar 12, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- thomast1906/github-copilot-agent-skills★ 203same name
- apisec-inc/apisec-skills★ 20same name
- DigitalExplorers/agent-skills★ 12same name
- Viprasol-Tech/api-security-review★ 0same 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 repository10 other files it gives its agents.
- apply-remediationSkill
- architecture-reviewSkill
- code-structureSkill
- correctness-reviewSkill
- data-consistencySkill
- implicit-state-machinesSkill
- infra-reviewSkill
- llm-app-reviewSkill
- perf-diagnosisSkill
- repo-audit-swarmSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
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.