bug-bounty SKILL.md skillF
bug-bounty from 26zl/cybersec-toolkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add 26zl/cybersec-toolkit/bug-bounty@git:20260730.b2c7e03Pins git:20260730.b2c7e03 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- F, 13 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- 26zl/cybersec-toolkit
- Path
.claude/skills/bug-bounty/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260730.b2c7e03, committed Jul 30, 2026
- First version recorded
- Jun 13, 2026
- Size
- 76,715 bytes
- Repository stars
- 100
- License
- MIT
Complete bug bounty workflow — recon (subdomain enumeration, asset discovery, fingerprinting, HackerOne scope, source code audit), pre-hunt learning (disclosed reports, tech stack research, threat modeling), vulnerability hunting (IDOR, SSRF, XSS, auth bypass, CSRF, race conditions, SQLi, XXE, file upload, business logic, GraphQL, HTTP smuggling, cache poisoning, OAuth, OIDC, SSTI, subdomain takeover, cloud misconfig, ATO chains, agentic AI), LLM/AI security testing…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
> **Vendored note (this repo).** Adapted from the standalone [claude-bug-bounty](https://github.com/shuvonsec/claude-bug-bounty) project. The upstream **executable scaffolding** — helper scripts (`tools/*.py`, `tools/*.sh`), the standalone `wordlists/` pipeline, and slash-commands (`/recon`, `/hunt`, `/validate`, `/report`, …) — is **not bundled here**: run tooling through the MCP server (`run_tool` / `run_pipeline` / `run_script`) and install via the project installer/registry. Any static deep-dive files this skill needs are vendored into its own `references/` folder, and cross-skill references resolve by skill name (e.g. the `bb-methodology` skill). Some named tools may not be in `tools_config.json` yet — add them with the `add-tool` skill or install upstream. # Bug Bounty Master Workflow Full pipeline: Recon -> Learn -> Hunt -> Validate -> Report. One skill for everything. ## THE ONLY QUESTION THAT MATTERS > **"Can an attacker do this RIGHT NOW against a real user who has taken NO unusual actions -- and does it cause real harm (stolen money, leaked PII, account takeover, code execution)?"** > > If the answer is NO -- **STOP. Do not write. Do not explore further. Move on.** …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_23olb7zd3n56arbe/58a610e429666c21c4d4d5fa75d287faf6cb9889658a6aff80ac26ac508b9546.json
Then /plugin install bug-bounty@markdownregistry-23olb7zd3n56arbe in Claude Code. It installs git:20260730.b2c7e03, the one graded F here, pinned to the commit it was graded at, and leaves it there.
mdr add 26zl/cybersec-toolkit/bug-bounty@sha256:58a610e429666c21The line at the top of this page pins the label git:20260730.b2c7e03, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_23olb7zd3n56arbe)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in 26zl/cybersec-toolkit/bug-bounty since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of bug-bounty from somewhere else? Ask it: where did my bug-bounty come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Jun 13, 2026 and Jul 30, 2026, about one every 47 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260730.b2c7e03 latest | 2026-07-30 | b2c7e03 | 76,715 B | F | view · diff |
| git:20260613.a7dba45 | 2026-06-13 | a7dba45 | 77,121 B | F | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/bug-bounty/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- FAIL, critical: No instruction hidden inside an HTML comment (matched: <!-- ignore previous instructions -->)
- FAIL, critical: No link to an exfiltration or paste host (matched: https://ATTACKER.burpcollaborator)
- fail: No prompt-injection phrasing (matched: ignore previous instructions)
- fail: No link to a raw IP address (matched: http://169.254.169.254)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (76715 bytes)
- pass: No zero-width or bidi control characters
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
26zl/cybersec-toolkit · 100 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_23olb7zd3n56arbe GET https://markdownregistry.com/api/v1/resolve?ref=26zl/cybersec-toolkit/bug-bounty GET https://markdownregistry.com/api/v1/blob/58a610e429666c21c4d4d5fa75d287faf6cb9889658a6aff80ac26ac508b9546
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from 26zl/cybersec-toolkit
Every file in 26zl/cybersec-toolkit