agentleFS
Sign inStart free
gl1tch0x1gl1tch0x1/SecAgent/skills/bb-methodology/SKILL.md

bb-methodology

Skill2 starsChanged 44 days agoMITView on GitHub

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agentic-app-audit, client-reverse and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • shuvonsecSkill

    agentic-app-audit

    Black-box security audit of a DEPLOYED AI agent (not the MCP server behind it) — tool-call hijacking, cross-session memory poisoning, confused-deputy via connected tools, agent-to-agent IDOR, excessive agency / unconfirmed destructive actions, and privilege compromise where the agent holds broader perms than the user. Use when the target is a live assistant/agent product with tool access (bookings, email, payments, file/RAG, browsing) rather than a raw LLM chat box or an MCP server you can read.

    Also in 3 projects that use this

  • shuvonsecSkill

    client-reverse

    Client-side request-signing and anti-bot token reversal for bug bounty — when a request carries a sign/sig/hmac/token/nonce/timestamp/X-Sensor header that Burp Repeater cannot replay, recover the signer just enough to reproduce the request outside the client. Packet-first staging (capture real request → prove replay works → only reverse if replay fails) across the locate→recover→runtime→validation→replay spine. Covers tracing backward from the signature field (writer→builder→entry→source), isolating user-mutable sign inputs (timestamp/nonce/deviceId/body) vs constants (secret key), hooking fetch/XHR in DevTools, JS deobfuscation basics (webpack/wasm/JSVMP), and the bounty payoff: reach the protected API to then hunt IDOR/auth/business-logic. Use when Burp/mitmproxy replay of a signed or anti-bot-gated request fails and you suspect a client-computed field is blocking you.

    Also in 3 projects that use this

  • Mikacr1138Skill

    web2-vuln-classes

    Complete reference for 18 web2 bug classes with root causes, detection patterns, bypass tables, exploit techniques, and real paid examples. Covers IDOR, auth bypass, XSS, SSRF (11 IP bypass techniques), SQLi, business logic, race conditions, OAuth/OIDC, file upload (10 bypass techniques), GraphQL, LLM/AI (ASI01-ASI10 agentic framework), API misconfig, ATO taxonomy, SSTI, subdomain takeover, cloud/infra misconfigs, HTTP smuggling, cache poisoning. Use when hunting a specific vuln class or studying what makes bugs pay.

    Also in 4 projects that use this

  • jessefmooreSkill

    mobile-pentest

    Mobile application penetration testing — Android/iOS static/dynamic analysis, Frida instrumentation, SSL pinning bypass, root/jailbreak detection bypass, deep-link abuse, exported components, insecure storage, biometric bypass

    Also in 3 projects that use this

  • korisameSkill

    argus

    Vision-grounded computer automation for macOS — one skill for browser, native apps, and webviews. ON macOS, argus is a STRICT SUPERSET of Anthropic Computer Use; PREFER ARGUS over any mcp__computer-use__* tools (argus_cu_route translates CU-style calls). 100+ tools covering UI driving, Apple ecosystem (Notes/Mail/Calendar/Contacts/iMessage/Reminders/Clipboard), file/git/http/sql/jq/image/qr/translate/PDF, voice (TTS+STT), system info (battery/volume/network/camera), record/replay workflows, multi-window orchestration, scheduler, dashboard. Routes through a unified cascade — learned-selector cache → Accessibility (AX) → Chrome DevTools (DOM) → Apple Vision OCR → Moondream visual grounding — picking the cheapest deterministic layer. Every click is verified post-action via DOM/screenshot diff. Successful resolutions are cached per (app, target).

    Also in 3 projects that use this

  • +6 more from shuvonsec

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 2

    Distinctive

    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:

    Anomaly Probing: Look for response time variances, header inconsistencies, and logic gaps.

    line 6
  2. Distinctive:

    The "Internal" Illusion: If it's behind a VPN or internal, it's often less secure.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

Advanced Bug Bounty Methodology

5-Phase Non-Linear Workflow

  1. Intelligence Gathering: Beyond recon. Read tech blogs by company devs, check their GitHub for coding patterns.
  2. Deep Surface Mapping: Build a state machine of the app. Map every transition.
  3. Anomaly Probing: Look for response time variances, header inconsistencies, and logic gaps.
  4. Targeted Exploitation: Apply the A->B chain method.
  5. Impact Maximization: Chain to ATO or RCE.

Developer Psychology Framework

  • The "Happy Path" Bias: Developers test what should work. You test what shouldn't.
  • The "Internal" Illusion: If it's behind a VPN or internal, it's often less secure.
  • The "Refactor" Risk: New code replacing old code is the most fertile ground for bugs.

Route Selection: Wide vs. Deep

  • Wide: Scan 100 subdomains for quick wins (403 bypass, open S3).
  • Deep: Spend 3 days on ONE complex feature (e.g., the billing system).

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