API Security Hardening
$2.99OfficialHarden APIs against attacks: input validation, output encoding, rate limiting, CORS, CSP, and injection prevention.
What you get
- ✓10-step procedure
- ✓6 pitfalls to avoid
- ✓Installs into 6 tools
- Version
- v1 →
- Last updated
- today
- Length
- 4 min read
- Requires
- Best with a strong model (Claude Sonnet 4)
Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes · Handles multi-file projects
Preview
When to use
Use this skill when hardening a REST or GraphQL API for production: designing input validation, output encoding, rate limiting, authentication/authorization enforcement, and the browser-facing controls (CORS, CSP, security headers). It maps directly to the OWASP API Security Top 10 and is appropriate for new APIs and for auditing existing ones. It assumes authn/authz design is handled elsewhere (see Authentication Flow Architect) and focuses on the API surface itself.
Inputs to gather
- API style and transport: REST, GraphQL, gRPC, WebSocket; HTTP/1.1 vs HTTP/2; JSON vs other bodies.
- Framework in use: Express, Fastify, Spring, Django/FastAPI, ASP.NET, Gin, Laravel — ea
…
🔒 Buy once ($2.99) to unlock the full playbook, download it, and install it in every tool you use.