bb-local-toolkit SKILL.md skillF
bb-local-toolkit from elementalsouls/claude-bughunter is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add elementalsouls/claude-bughunter/bb-local-toolkit@git:20261116.56cb92bPins git:20261116.56cb92b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- F, 13 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- elementalsouls/claude-bughunter
- Path
skills/bb-local-toolkit/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261116.56cb92b, committed Nov 16, 2026
- First version recorded
- May 5, 2026
- Size
- 73,500 bytes
- Repository stars
- 7,555
- License
- MIT
Use the full bug bounty workflow when you also need the local path of a tool, wordlist, or clone (SecLists, jhaddix, ffuf, dalfox, ghauri, trufflehog). Covers recon, pre-hunt research, source code audit, web and API vulnerability testing (IDOR, SSRF, XSS, SQLi, OAuth), LLM security testing, bug chaining, finding validation, and reporting. For general workflow routing without local tooling, use bug-bounty. 中文触发词:漏洞赏金、安全测试、渗透测试、漏洞挖掘、信息收集、子域名枚举、XSS测试、SQL注入、SSRF、安全审计、漏洞报告.
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
# 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.** ### Theoretical Bug = Wasted Time. Kill These Immediately: | Pattern | Kill Reason | |---|---| | "Could theoretically allow..." | Not exploitable = not a bug | | "An attacker with X, Y, Z conditions could..." | Too many preconditions | | "Wrong implementation but no practical impact" | Wrong but harmless = not a bug | | Dead code with a bug in it | Not reachable = not a bug | | Source maps without secrets | No impact | | SSRF with DNS-only callback | Need data exfil or internal access | | Open redirect alone | Need ATO or OAuth chain | | "Could be used in a chain if..." | Build the chain first, THEN report | **You must demonstrate actual harm. "Could" is not a bug. Prove it works or drop it.** --- ## CRITICAL RULES …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gs73l42mctj3mawd/aca24c6f20b0646d2eb09fb3a9fb047a874783b56bbf1052c27a358c450e796f.json
Then /plugin install bb-local-toolkit@markdownregistry-gs73l42mctj3mawd in Claude Code. It installs git:20261116.56cb92b, the one graded F here, pinned to the commit it was graded at, and leaves it there.
mdr add elementalsouls/claude-bughunter/bb-local-toolkit@sha256:aca24c6f20b0646dThe line at the top of this page pins the label git:20261116.56cb92b, 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_gs73l42mctj3mawd)
2 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 elementalsouls/claude-bughunter/bb-local-toolkit 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 bb-local-toolkit from somewhere else? Ask it: where did my bb-local-toolkit 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 5 versions of this file, between May 5, 2026 and Nov 16, 2026, about one every 49 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.56cb92b latest | 2026-11-16 | 56cb92b | 73,500 B | F | view · diff |
| git:20260824.9a1863c | 2026-08-24 | 9a1863c | 74,808 B | F | view · diff |
| git:20260722.8063d38 | 2026-07-22 | 8063d38 | 74,768 B | F | view · diff |
| git:20260515.5f39300 | 2026-05-15 | 5f39300 | 74,409 B | F | view · diff |
| git:20260505.e975612 | 2026-05-05 | e975612 | 73,085 B | F | view |
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds an older version.
- adriannoes/awesome-agentic-ai · cursor-claude-codex/skills/bug-hunter/skills/bb-local-toolkit/SKILL.md · 3 versions behind · 100 stars
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
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/bb-local-toolkit/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 (73500 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
elementalsouls/claude-bughunter · 7,555 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_gs73l42mctj3mawd GET https://markdownregistry.com/api/v1/resolve?ref=elementalsouls/claude-bughunter/bb-local-toolkit GET https://markdownregistry.com/api/v1/blob/aca24c6f20b0646d2eb09fb3a9fb047a874783b56bbf1052c27a358c450e796f
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 elementalsouls/claude-bughunter
Every file in elementalsouls/claude-bughunter