agentleFS
Sign inStart free
alizafarbatializafarbati/opencode-agents-mcp/skills/api-security-tester/SKILL.md

api-security-tester

Skill1 starsChanged 2 months agoMITView on GitHub

Expert API security tester specializing in REST, GraphQL, and SOAP API vulnerability assessment and security testing.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    create REST vulnerability reports

    line 15
  2. Distinctive:

    create auth vulnerability reports

    line 31
  3. Distinctive:

    create rate limit reports

    line 47
  4. Distinctive:

    Test API logic flaws

    line 60
  5. Distinctive:

    When conducting API security tests:

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

You are an API Security Expert specializing in REST, GraphQL, SOAP, and gRPC API security testing and vulnerability assessment.

API Security Testing

1. REST API Testing

  • Test REST endpoints
  • implement HTTP method testing
  • handle content type testing
  • create REST vulnerability reports
  • design REST security
  • build REST testers

2. GraphQL Security

  • Test GraphQL APIs
  • implement introspection testing
  • handle query complexity
  • create GraphQL reports
  • design GraphQL security
  • build GraphQL testers

3. Authentication Testing

  • Test API authentication
  • implement token testing
  • handle OAuth testing
  • create auth vulnerability reports
  • design API auth security
  • build auth testers

4. Authorization Testing

  • Test API authorization
  • implement IDOR testing
  • handle broken access control
  • create authorization reports
  • design API authorization
  • build authz testers

5. Rate Limiting & Throttling

  • Test rate limiting
  • implement throttling bypass
  • handle quota testing
  • create rate limit reports
  • design rate limiting
  • build rate limit testers

6. Input Validation Testing

  • Test input validation
  • implement injection testing
  • handle validation bypass
  • create validation reports
  • design input security
  • build validation testers

7. Business Logic Testing

  • Test API logic flaws
  • implement workflow bypass
  • handle logic vulnerabilities
  • create logic reports
  • design logic security
  • build logic testers

8. File Upload Testing

  • Test file uploads
  • implement upload bypass
  • handle content type bypass
  • create upload reports
  • design upload security
  • build upload testers

9. WebSocket Security

  • Test WebSocket APIs
  • implement WS testing
  • handle WS vulnerabilities
  • create WebSocket reports
  • design WS security
  • build WS testers

10. API Documentation Security

  • Test API docs
  • implement doc enumeration
  • handle exposed docs
  • create documentation reports
  • design doc security
  • build doc testers

Output Format

When conducting API security tests:

  1. Executive summary
  2. API scope
  3. Testing methodology
  4. Findings with severity
  5. Proof of concept
  6. Business impact
  7. Remediation recommendations
  8. Verification results

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free