api-security-testing — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited api-security-testing (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
⚠️ AUTHORIZED USE ONLY This skill is for educational purposes or authorized security assessments only. You must have explicit, written permission from the system owner before using this tool. Misuse of this tool is illegal and strictly prohibited.
Mandatory confirmation gate Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target: 1. Ask the user to state the exact target URL, IP, account, or resource. 2. Ask the user to confirm written authorization and the permitted scope. 3. Show the exact command(s) and explain their expected effect. 4. Wait for explicit confirmation in the current conversation.
>
Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.
Specialized workflow for testing REST and GraphQL API security including authentication, authorization, rate limiting, input validation, and API-specific vulnerabilities.
Use this workflow when:
Select approved phases and test accounts; do not dispatch every listed skill automatically. Use owned fixtures for destructive methods, injections, brute-force, resource exhaustion and deep/complex GraphQL requests. Define request, concurrency, byte and duration limits, stop conditions and cleanup before testing. Keep third-party systems and real customer data out of tests. Public schemas, missing headers and an HTTP success response alone do not prove an authorization flaw or exploitable limit bypass. Record untested endpoints and observed impact instead of checking “all endpoints tested” by assumption.
#### Skills to Invoke
api-fuzzing-bug-bounty - API fuzzingscanning-tools - API scanning#### Actions
#### Copy-Paste Prompts
Use @api-fuzzing-bug-bounty to discover API endpoints#### Skills to Invoke
broken-authentication - Auth testingapi-security-best-practices - API auth#### Actions
#### Copy-Paste Prompts
Use @broken-authentication to test API authentication#### Skills to Invoke
idor-testing - IDOR testing#### Actions
#### Copy-Paste Prompts
Use @idor-testing to test API authorization#### Skills to Invoke
api-fuzzing-bug-bounty - API fuzzingsql-injection-testing - Injection testing#### Actions
#### Copy-Paste Prompts
Use @api-fuzzing-bug-bounty to fuzz API parameters#### Skills to Invoke
api-security-best-practices - Rate limiting#### Actions
#### Copy-Paste Prompts
Use @api-security-best-practices to test rate limiting#### Skills to Invoke
api-fuzzing-bug-bounty - GraphQL fuzzing#### Actions
#### Copy-Paste Prompts
Use @api-fuzzing-bug-bounty to test GraphQL security#### Skills to Invoke
api-security-best-practices - Error handling#### Actions
#### Copy-Paste Prompts
Use @api-security-best-practices to audit API error handlingsecurity-audit - Security auditingweb-security-testing - Web securityapi-design-principles - API contract design~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.