bug bounty pattern library

    1

    A security research assistant that transforms authorized findings into professional, evidence-based bug bounty reports.

    $5

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned

    Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    bug bounty pattern library

    Example session with this skill installed

    I found that I can change the 'user_id' parameter in the /api/v1/profile/view request from my own ID to another user's ID and see their email address. Prepare a triage analysis.

    • Read your context and instructions
    • Compiled the bug bounty pattern
    • Generated the document

    I have analyzed the observation regarding the /api/v1/profile/view endpoint. This finding indicates a potential Insecure Direct Object Reference (IDOR) vulnerability.

    Triage Analysis: IDOR in Profile API

    FindingPatternConfidenceImpactSeverityEvidence StatusNext Action
    Unauthorized PII AccessAuthorization -> BOLAConfirmedHigh (Privacy)MediumNeeds Response BodyVerify with 2nd Test Account

    Quick Analysis

    Pattern: Broken Object Level Authorization (BOLA / IDOR)
    Confidence: Confirmed (Behavior verified by parameter manipulation)
    Why it matters: It allows an authenticated user to access sensitive Private Identifiable Information (PII), such as email addresses, belonging to other users without authorization.
    Safe validation: Register two distinct test accounts (User A and User B). Attempt to access User B's profile using User A's session by modifying the user_id in the GET request.
    Evidence needed: Request/Response pairs showing User A's session cookie retrieving User B's data, with sensitive values (tokens/passwords) redacted.
    Potential impact: Mass data exfiltration of the user database, leading to GDPR/privacy compliance violations and reputational damage.

    Remediation

    Implement an authorization check at the data access layer. Ensure the application verifies that the user_id associated with the active session token has the permission to view the requested user_id object before returning the record.

    Next steps

    1. Perform the cross-account validation using two controlled test users.
    2. Capture the full HTTP request and response for the report.
    3. Draft the final report using the "Full Finding" template once evidence is attached.

    bug-bounty-pattern-library.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Convert raw proxy logs into structured security hypotheses.Draft professional vulnerability reports for bug bounty programs.Categorize security findings into standard vulnerability patterns.Generate remediation guidance for developers based on findings.

    About this skill

    The problem

    Translating raw security observations into professional bug bounty reports is time-consuming and prone to severity inflation. Developers often struggle to bridge the gap between a technical glitch and a documented security impact that triage teams will actually accept.

    What it does

    • Maps raw reconnaissance data to established security patterns like IDOR, CSRF, and logic flaws.
    • Generates step-by-step reproduction guides focusing on low-impact, safe validation methods.
    • Structures technical evidence into professional report formats compatible with HackerOne or Bugcrowd.
    • Calculates severity rationale based on exploitability, prerequisites, and business impact.
    • Provides developer-centric remediation guidance for identified vulnerabilities.

    Why this beats prompting it yourself

    General-purpose models often hallucinate severity or suggest destructive payloads that violate program terms. This skill enforces a structured investigation workflow, ensuring every finding is categorized correctly and supported by an evidence checklist before a report is generated.

    Use cases

    • Transforming Burp Suite or Proxy logs into structured vulnerability hypotheses.
    • Drafting professional bug bounty reports for authorized private or public programs.
    • Triaging multiple security observations to identify the root cause vs. symptoms.
    • Creating safe, non-destructive proof-of-concept steps for sensitive production environments.

    Known limitations

    Requires explicit user confirmation of authorization before analyzing target-specific data. Does not provide weaponized exploit code or tools for bypassing security monitoring.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 21 days ago

    • Passed all security checks, Safe to install

    Listed21 days ago

    What's inside

    Frequently Asked Questions