SKILLEMALL.ai
GitHub ↗ RU Sign in

AB API Fuzzing for Bug Bounty

This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 2 478 tokens Open the sourcegithub.com↗ analyzed 2 d ago

This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API…

As a process B 66/100 · Nearly there — weak spots: consistency, running it twice, progress reporting

IntegrationGitHubSecurityWriting and documentsFinancetype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
96
Quality 40%
85
Run on models
none yet
Process rating
B
66/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
Consistency w 8
40
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 4

    ✓ No critical or high findings

    Medium and low: 4
    • low Risky intent intent-offensive-security SKILL.md:2
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      name: API Fuzzing for Bug Bounty
    • low Risky intent intent-offensive-security SKILL.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
      description: This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API
      quoted
    • low Risky intent intent-offensive-security SKILL.md:9
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # API Fuzzing for Bug Bounty
    • low Risky intent intent-offensive-security SKILL.md:13
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Provide comprehensive techniques for testing REST, SOAP, and GraphQL APIs during bug bounty hunting and penetration testing engagements. Covers vulnerability discovery, authentication bypass, IDOR exp

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)

    Process rating: all ten parameters 66/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 2 mutating operations with no state check
    • 40Consistency. Frontmatter name (API Fuzzing for Bug Bounty) differs from the folder (api-fuzzing-bug-bounty)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web, python) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 19 steps
    • 100Execution cost. Instruction body is 2478 tokens
    • low 14 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • -2localhost URLs: will not work for another user
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 7 example trigger phrases
    • +3Description length 253: enough signal without eating the budget
    • +4Structure: 31 headings
    • +3Step-by-step instructions: 19 items
    • +3Output format is stated explicitly
    • +4Has examples (22 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.