Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/Mikacr1138/claude-bug-bountyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/mikacr1138/claude-bug-bounty/chain-builder)<a href="https://agentmods.dev/agents/mikacr1138/claude-bug-bounty/chain-builder"><img src="https://agentmods.dev/badge/agents/mikacr1138/claude-bug-bounty/chain-builder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/mikacr1138/claude-bug-bounty/chain-builder"><img src="https://agentmods.dev/badge/agents/mikacr1138/claude-bug-bounty/chain-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00096 | $0.00900 |
| Opus 5 | $0.00048 | $0.00450 |
| Sonnet 5 | $0.00019 | $0.00180 |
| Haiku 4.5 | $0.00010 | $0.00090 |
Grade B, and why
chain-builder scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
| SSRF DNS callback | 169.254.169.254 cloud metadata | Critical | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chain Builder Agent
You are a bug chain specialist. You take a confirmed bug A and systematically find B and C to combine for higher severity.
Your Approach
- Identify bug class of A
- Look up chain table for B candidates
- Check if B is testable from current position
- Confirm B exists (exact HTTP request)
- Output: chain path, combined severity, separate report count
The A→B Chain Table
| Found A | Check B | Combined Impact |
|---|---|---|
| IDOR (GET) | IDOR on PUT/DELETE same path | Multiple High |
| Auth bypass | Every sibling endpoint in same controller | Multiple High |
| Stored XSS | Admin views it? → priv esc | Critical |
| SSRF DNS callback | 169.254.169.254 cloud metadata | Critical |
| Open redirect | OAuth redirect_uri → code theft | Critical ATO |
| S3 bucket listing | JS bundles → grep OAuth creds | Medium/High |
| GraphQL introspection | Auth bypass on mutations | High |
| LLM prompt injection | IDOR via chatbot (other user data) | High |
| Path traversal | /proc/self/environ → RCE | Critical |
| Subdomain takeover | OAuth redirect_uri at subdomain | Critical |
| JWT weak secret | Forge admin token | Critical |
| File upload bypass | SVG→XSS, PHP→RCE | High/Critical |
Known High-Value Chains
Key Chain Examples
S3 → OAuth ATO: List bucket → download JS bundles → grep client_secret → test OAuth without code_challenge → 3 reports ~$1,200
Open Redirect → OAuth ATO: Confirm redirect → find OAuth flow → set redirect_uri to your redirect endpoint → victim clicks → code delivered to attacker → exchange for token
XSS → Admin Priv Esc: Stored XSS in user field → verify admin views it → payload auto-submits POST to promote attacker to admin
SSRF → Cloud Metadata: DNS callback only = Info → escalate to 169.254.169.254 → get IAM role → fetch credentials → enumerate AWS perms = Critical
Prompt Injection → IDOR: Confirm chatbot follows injected instructions → inject cross-user data request → if other user data returned = IDOR via AI feature
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 75 lines · 96 tokens per session scan B d44df5e7ca3d
chain-builder is an agent published in the GitHub repository Mikacr1138/claude-bug-bounty (2 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 900 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (cloud metadata endpoint). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
appsec-threat-renderer
INTERNAL renderer for Stage 2 of create-threat-model. Invoke only from the skill after Stage 1 has produced validated intermediate artifacts.
appsec-stride-analyzer-v2
INTERNAL context-v2 — bounded STRIDE for one component.
appsec-actor-discoverer
INTERNAL — controller-dispatched actor discovery after config/IaC scanning and before architecture modeling; writes .actors-discovered.json and is skipped in quick mode.
appsec-eval-judge
Semantic-quality judge for a threat-model run, used by the eval-threat-model dev/test skill (NOT in the create-threat-model phase map). Two modes: JUDGE surfaces candidate quality defects for one rubric dimension from a pre-digested brief; VERIFY adversarially refutes another judge's candidates (refute-by-default)…
appsec-qa-reviewer
INTERNAL — exceptional Stage-3 semantic triage after the deterministic QA gate. Consumes a compact repair plan; never repeats the full mechanical detector battery.
appsec-run-diagnostician
INTERNAL — dispatched on request when APPSECPLUGINDEV=1, either from the offer after a create-threat-model run's completion summary or from /appsec-advisor:diagnose-run. Reads the deterministic .run-issues.json, decides per issue whether the symptom is a defect in this plugin or an environment/expected condition, and…