bug-bounty SKILL.md skillF
bug-bounty from novaestellar/novahaku is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add novaestellar/novahaku/bug-bounty@git:20260927.e881f8aPins git:20260927.e881f8a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- F, 13 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- novaestellar/novahaku
- Path
testing/hunt/bug-bounty/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260927.e881f8a, committed Sep 27, 2026
- First version recorded
- Sep 3, 2026
- Size
- 76,380 bytes
- Repository stars
- 28
- 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
mdr add novaestellar/novahaku/bug-bounty@sha256:8bb5958534dff91cThe line at the top of this page pins the label git:20260927.e881f8a, 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_lnas43ctek72tl2b)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Sep 3, 2026 and Sep 27, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.e881f8a latest | 2026-09-27 | e881f8a | 76,380 B | F | view · diff |
| git:20260925.b22b1f8 | 2026-09-25 | b22b1f8 | 76,383 B | F | view · diff |
| git:20260925.de1a6a8 | 2026-09-25 | de1a6a8 | 76,397 B | F | view · diff |
| git:20260910.546fe86 | 2026-09-10 | 546fe86 | 77,933 B | F | view · diff |
| git:20260903.05528be | 2026-09-03 | 05528be | 77,800 B | F | view · diff |
| git:20260903.29924dd | 2026-09-03 | 29924dd | 77,959 B | F | view · diff |
| git:20260903.fa855c4 | 2026-09-03 | fa855c4 | 77,930 B | F | view |
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 (76380 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
novaestellar/novahaku · 28 stars · license MIT · pushed 2026-09-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lnas43ctek72tl2b GET https://markdownregistry.com/api/v1/resolve?ref=novaestellar/novahaku/bug-bounty GET https://markdownregistry.com/api/v1/blob/8bb5958534dff91c054aec0e46b8549cee4afcbe7aa4f09fb99183b921c4274e
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 novaestellar/novahaku
Every file in novaestellar/novahaku