Api security best practices
Shared library of AI agent skills — works across Claude Code, Cursor, Codex, Windsurf, OpenCode, and Google Antigravity via a single universal installer.
npx -y skills add newmindsgroup/ai-agent-skills-library --skill api-security-best-practicesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.8 KB, 469 tokens by cl100k_base, as published. Nobody here has run it
API Security Best Practices
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities
When to Use
- The request matches the skill description: Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities
- The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.
- The work would benefit from the complete guidance preserved in
references/full-guidance.md.
Core Workflow
- Confirm the request matches this skill's trigger, scope, and risk profile.
- Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
- Load
references/full-guidance.mdwhen implementation details, examples, anti-patterns, validation checks, or edge cases are needed. - Apply only the relevant guidance instead of loading or repeating the entire reference by default.
- Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.
Topic Map
- Overview
- When to Use This Skill
- How It Works
- Step 1: Authentication & Authorization
- Step 2: Input Validation & Sanitization
- Step 3: Rate Limiting & Throttling
- Step 4: Data Protection
- Step 5: API Security Testing
- Examples
- Example 1: Implementing JWT Authentication
- Secure JWT Authentication Implementation
- Authentication Flow
- Implementation
- Security Best Practices
- Example 2: Input Validation and SQL Injection Prevention
- Preventing SQL Injection and Input Validation
- The Problem
- The Solution
Reference Map
references/full-guidance.mdpreserves the complete original guidance, including examples and detailed edge cases.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Progressive Loading
Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.