Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Quality-Max/free-qa-skills --skill api-security-scangit clone --depth 1 https://github.com/Quality-Max/free-qa-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/quality-max/free-qa-skills/api-security-scan)<a href="https://agentmods.dev/skills/quality-max/free-qa-skills/api-security-scan"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/api-security-scan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/quality-max/free-qa-skills/api-security-scan"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/api-security-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00053 | $0.00588 |
| Opus 5.5 | $0.00021 | $0.00235 |
| Sonnet 5.5 | $0.00011 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
api-security-scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Security Scan
Find the security holes in your API design before they ship. Read-only: it flags issues with file:line, it doesn't change your code.
Prerequisites
- None. Pure Claude Code — reads your OpenAPI/Swagger spec or route/handler code directly, no MCP required.
Trigger
- "Security review my API / OpenAPI spec"
- "Check my endpoints for missing auth"
- "API security scan"
Workflow
- Locate the API surface: an OpenAPI/Swagger file if present, otherwise the route definitions and handlers.
- Review each endpoint against the checks below; report
pathorfile:line, severity, and the fix.
What to flag
| Risk | What to look for |
|---|---|
| Missing authentication | Endpoints with no auth requirement that expose data or actions |
| Broken object-level auth (IDOR/BOLA) | Resources fetched by ID with no ownership/authorization check |
| Missing function-level auth | Admin/privileged operations reachable by normal users |
| No rate limiting | Auth, search, or expensive endpoints with no throttling (brute-force / DoS) |
| Verbose errors | Stack traces, SQL, or internal details returned to clients |
| Sensitive data in URLs | Tokens, passwords, or PII in query strings (logged everywhere) |
| Mass assignment | Request bodies bound to models without an allowlist of fields |
| CORS misconfig | Wildcard origin combined with credentials |
| Missing input validation | Body/query/path params accepted without schema/type checks |
| No pagination limits | List endpoints that can return unbounded result sets |
| Secrets in examples | Real keys/tokens in spec examples or sample requests |
- Output a severity-ranked report:
## API Security Scan
**2 high, 1 medium**
### HIGH
- GET /users/{id} — no ownership check; any authenticated user can read any
record (BOLA). Enforce that the caller owns or may access {id}.
- POST /login — no rate limiting; vulnerable to credential brute-force. Add
per-IP/per-account throttling and lockout.
### MEDIUM
- GET /search — returns full stack traces on error. Return a generic message;
log details server-side.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 63 lines · 53 tokens per session scan A f9f7f5711961
api-security-scan is a skill published in the GitHub repository Quality-Max/free-qa-skills (13 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 588 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
api-contracts
API design and contract engineering — REST resource modelling, error envelopes, pagination, filtering, idempotency, versioning and deprecation, rate limiting, webhooks, OpenAPI, GraphQL schema and N+1 defence, and contract testing. Use when designing, reviewing or documenting an endpoint or integration; when the user…
performance-engineering
Performance engineering across the stack — Core Web Vitals (LCP, INP, CLS), bundle size and rendering strategy, image and font optimisation, backend latency budgets, caching layers, database query cost, profiling, and load testing. Use when the user says "slow", "performance", "optimize", "Core Web Vitals", "LCP"…
interface-auditor
Detect UX antipatterns (smells) in interface descriptions using the uxuiprinciples smell taxonomy. Returns structured findings with matched symptoms, severity, and step-by-step remediation recipes. API key optional — full remediation recipes require uxuiprinciples.com API Access.
uxui-evaluator
Evaluate interface descriptions against 195 research-backed UX/UI principles. Returns structured findings with severity, remediation, and business impact. API key optional — enriched output requires uxuiprinciples.com API Access.
link-purpose
Analyzes code for WCAG 2.4.4 Link Purpose (In Context) compliance. Identifies generic link text, ambiguous links, and links without sufficient context. Recommends descriptive link text and proper ARIA attributes.