Specialized workflow for testing REST and GraphQL API security including authentication, authorization, rate limiting, input validation, and API-specific vulnerabilities.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionapi-security-testingExecute the skills CLI command in your project's root directory to begin installation:
Fetches api-security-testing from sickn33/antigravity-awesome-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate api-security-testing. Access via /api-security-testing in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
31.1K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
31.1K
stars
Specialized workflow for testing REST and GraphQL API security including authentication, authorization, rate limiting, input validation, and API-specific vulnerabilities.
Use this workflow when:
api-fuzzing-bug-bounty - API fuzzingscanning-tools - API scanningUse @api-fuzzing-bug-bounty to discover API endpoints
broken-authentication - Auth testingapi-security-best-practices - API authUse @broken-authentication to test API authentication
idor-testing - IDOR testingUse @idor-testing to test API authorization
api-fuzzing-bug-bounty - API fuzzingsql-injection-testing - Injection testingUse @api-fuzzing-bug-bounty to fuzz API parameters
api-security-best-practices - Rate limitingUse @api-security-best-practices to test rate limiting
api-fuzzing-bug-bounty - GraphQL fuzzingUse @api-fuzzing-bug-bounty to test GraphQL security
api-security-best-practices - Error handlingUse @api-security-best-practices to audit API error handling
security-audit - Security auditingweb-security-testing - Web securityapi-development - API developmentPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
sickn33/antigravity-awesome-skills
shadcn/improve
api-security-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
api-security-testing is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: api-security-testing is focused, and the summary matches what you get after install.
api-security-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend api-security-testing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
api-security-testing reduced setup friction for our internal harness; good balance of opinion and flexibility.
api-security-testing has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend api-security-testing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
api-security-testing fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend api-security-testing for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 65