charlieviettq/awesome-agent-skill / .claude/skills/api-security-testing
api-security-testing
VerifiedSecurity testing checklist for HTTP APIs—authn/z, input validation, rate limits, sensitive data exposure, and common OWASP API issues. Use when reviewing or testing REST/GraphQL endpoints before release.
API security testing
Preconditions
- Test in non-production unless explicitly authorized.
- Use dedicated test accounts; never real customer PII in payloads.
Test matrix (prioritized)
Authentication and session
- Missing/invalid token rejected (401)
- Expired or revoked credentials rejected
- Session fixation / cookie flags (HttpOnly, Secure, SameSite) where applicable
Authorization
- Horizontal: user A cannot access user B's resource IDs
- Vertical: non-admin cannot invoke admin routes
- IDOR on path/query/body identifiers
Input and abuse
- Oversized payloads rejected
- Injection surfaces parameterized (SQL, command, template)
- Rate limiting on auth and expensive endpoints
Data exposure
- Errors do not leak stack traces or secrets in prod-like config
- Responses omit internal fields (tokens, hashes, full PAN)
- Pagination does not bypass auth filters
Transport and config
- HTTPS enforced; HSTS where applicable
- CORS not
*with credentials - Security headers on API gateway if present
Web-facing surfaces (when API serves or pairs with UI)
- CSP or explicit script policy documented
- CSRF protection on cookie-based mutations
- Clickjacking headers (
X-Frame-Optionsor CSPframe-ancestors) where relevant - File upload: type/size limits, virus scan hook if required by policy
Reporting
For each finding: endpoint, steps, impact, severity, remediation, retest status.
Boundaries
- Defensive testing only; no unauthorized production scanning.
- For deep pen-test, engage formal AppSec process.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 193k | Updated | Claude CodeCodex | Verified | Install |