Home / mikacr1138 / claude-bug-bounty · GitHub

bug-bounty SKILL.md skillB

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

bug-bounty from mikacr1138/claude-bug-bounty is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add mikacr1138/claude-bug-bounty/bug-bounty@git:20260317.a154787

Pins git:20260317.a154787 in mdr.lock. Pin the fingerprint instead.

Audit grade: B, 16 of 17 checks passed
Kind: SKILL.md skill
Repository: mikacr1138/claude-bug-bounty
Path: skills/bug-bounty/SKILL.md
Versions recorded: 1
Latest version: git:20260317.a154787, committed Mar 17, 2026
Size: 48,172 bytes
Repository stars: 3
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, mind maps, threat modeling), vulnerability hunting (IDOR, SSRF, XSS, auth bypass, CSRF, race conditions, SQLi, XXE, file upload, business logic, GraphQL, HTTP smuggling, cache poisoning, OAuth, timing side-channels, OIDC, SSTI, subdomain takeover, cloud misconfig, ATO chains, agentic AI), LLM/AI security…

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

The exact contents, by fingerprint

mdr add mikacr1138/claude-bug-bounty/bug-bounty@sha256:0416ecfa1a702b23

The line at the top of this page pins the label git:20260317.a154787, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_rd7n75y5fnqrduvg.svg)](https://markdownregistry.com/a/art_rd7n75y5fnqrduvg)

6 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Mar 17, 2026.

version	committed	commit	size	audit
git:20260317.a154787 latest	2026-03-17	a154787	48,172 B	B	view

Audit of the latest version

B 16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

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 (48172 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 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

GitHub

mikacr1138/claude-bug-bounty · 3 stars · license MIT · pushed 2026-10-14 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_rd7n75y5fnqrduvg
GET https://markdownregistry.com/api/v1/resolve?ref=mikacr1138/claude-bug-bounty/bug-bounty
GET https://markdownregistry.com/api/v1/blob/0416ecfa1a702b23550cb087f43bf51eba859897c6bccfe092967db627462256

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.