bugbounty SKILL.md skillA
bugbounty from dragonked2/alphacode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dragonked2/alphacode/bugbounty@git:20261112.8445bdePins git:20261112.8445bde in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dragonked2/alphacode
- Path
src/alphacode_base/bundled_skills/bugbounty/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261112.8445bde, committed Nov 12, 2026
- First version recorded
- Nov 3, 2026
- Size
- 32,275 bytes
- Repository stars
- 626
- License
- MIT
Security assessment, vulnerability hunting, and code security audit — differential testing, 7-gate validation, hypothesis-driven, evidence-first. Covers OWASP Top 10, CWE mapping, SAST/DAST, CVSS scoring, injection (SQLi, XSS, SSTI, SSRF), auth bypass, IDOR, JWT, OAuth, API and GraphQL security, deserialization, and PoC reporting. Verifies whether something is genuinely a vulnerability and reports only what survives. Use when the user mentions bug bounty, security review, security audit…
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
# SECURITY REVIEW — EVIDENCE OVER IMPACT CHASING You are reviewing an application on behalf of its owner. Your job is to **determine what is actually wrong, prove it, and report it honestly** — not to maximize severity, not to reach the deepest possible foothold, and not to produce an impressive-looking list. A review that correctly reports "no vulnerability here" is a successful outcome. **The three failure modes this skill exists to prevent:** 1. **Impact inflation** — dressing up a low-severity issue as critical so it looks more valuable. Report the severity you can actually demonstrate. 2. **Escalation for its own sake** — chaining deeper after the bug is already proven. Proving a read-only IDOR does not require proving account takeover, and continuing past the point of proof creates risk the owner never agreed to and liability for you. 3. **Reporting designed behavior** — public profiles, error messages, and version banners are not vulnerabilities. Programs reject these routinely and they waste the owner's triage time. ## Investigation continuity ### Choose capabilities for the question …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_d3p65kfy4s7qgeie/ad1f1113c956a63cb999782767279b77ede8019cf77979129a75350a53731136.json
Then /plugin install bugbounty@markdownregistry-d3p65kfy4s7qgeie in Claude Code. It installs git:20261112.8445bde, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add dragonked2/alphacode/bugbounty@sha256:ad1f1113c956a63cThe line at the top of this page pins the label git:20261112.8445bde, 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_d3p65kfy4s7qgeie)
5 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 dragonked2/alphacode/bugbounty 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 bugbounty from somewhere else? Ask it: where did my bugbounty 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 Nov 3, 2026 and Nov 12, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261112.8445bde latest | 2026-11-12 | 8445bde | 32,275 B | A | view · diff |
| git:20261111.95d3917 | 2026-11-11 | 95d3917 | 29,739 B | A | view · diff |
| git:20261110.1041e0e | 2026-11-10 | 1041e0e | 29,203 B | A | view · diff |
| git:20261105.b5f0403 | 2026-11-05 | b5f0403 | 26,792 B | A | view · diff |
| git:20261103.b72aef9 | 2026-11-03 | b72aef9 | 25,578 B | A | 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/bugbounty/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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (32275 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- 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 link to a raw IP address
- pass: No script tag
Source
dragonked2/alphacode · 626 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d3p65kfy4s7qgeie GET https://markdownregistry.com/api/v1/resolve?ref=dragonked2/alphacode/bugbounty GET https://markdownregistry.com/api/v1/blob/ad1f1113c956a63cb999782767279b77ede8019cf77979129a75350a53731136
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.