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.
npx skills add Olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills --skill web3-triage-reportgit clone --depth 1 https://github.com/Olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skillsWrote 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/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-triage-report)<a href="https://agentmods.dev/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-triage-report"><img src="https://agentmods.dev/badge/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-triage-report/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/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-triage-report"><img src="https://agentmods.dev/badge/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-triage-report.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.00059 | $0.07633 |
| Opus 5 | $0.00030 | $0.03816 |
| Sonnet 5 | $0.00012 | $0.01527 |
| Haiku 4.5 | $0.00006 | $0.00763 |
Grade A, and why
web3-triage-report scanned grade A with 0 findings 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 12d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to web3-triage-report — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 790 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TRIAGE, REPORT WRITING & REAL EXAMPLES
PART 1: TRIAGE
THE 7-QUESTION GATE
Ask these IN ORDER before writing a single word of your report. ONE wrong answer = STOP and move on.
Q1: Can an attacker use this RIGHT NOW, step by step?
Complete this template:
1. Setup: [what I need]
2. Call: [exact function, exact params]
3. Result: [what I have that I didn't have before]
4. Cost: [gas + capital]
5. ROI: [profit / cost ratio]
If you cannot complete steps 2 and 3 with specific function calls: KILL IT.
Q2: Is the impact in the program's accepted impact list?
Go to the Immunefi program page. Find "Impacts in Scope." Match your bug to one of these EXACTLY.
Example impact tiers:
- "Direct theft of any user funds" — Critical
- "Permanent freezing of funds" — Critical
- "Protocol insolvency" — Critical
- "Theft of unclaimed yield" — High
- "Permanent freezing of unclaimed yield" — High
- "Temporary freezing of funds" — High
- "Smart contract unable to operate due to lack of token funds" — Medium
- "Griefing (no profit motive, but damage to users)" — Medium
- "Contract fails to deliver promised returns, but doesn't lose value" — Low
If your bug does not match any impact in scope: KILL IT.
Q3: Is the root cause in an in-scope contract?
Confirm the exact deployed address is in scope on the program page.
If the bug is in Aave, Uniswap, OpenZeppelin, or any external dependency: KILL IT.
Q4: Does it require admin/privileged access?
"Admin can drain funds" = centralization risk = KILL IT. "Admin can set parameter X which under condition Y creates DoS" = borderline.
Salvage path: can the bug trigger WITHOUT the admin doing anything unusual?
- If yes: valid
- If no: likely invalid (requires admin mistake — almost always out of scope)
Q5: Is this already known/acknowledged in prior audits?
Find the audit reports for the protocol. Search for "Risk Accepted," "Acknowledged," "Won't Fix."
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.
- 12d ago First seen · 790 lines · 59 tokens per session scan A 8f7e92bb2142
web3-triage-report is a skill published in the GitHub repository Olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills (5 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 7,633 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to web3-triage-report, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pwn-ai-agent-btc
Drive PWN::AI::Agent::BTC from pwneval.
pwn-blockchain-eth
Drive PWN::Blockchain::ETH from pwneval.
frontend-design
Create distinctive, production-grade Stellar dApp UI. Combines bold aesthetic direction with smart contract integration patterns — wallet connection flows, transaction UX, contract data displays, and agentic kit hook wiring. No generic "AI slop" aesthetics.
smart-contracts
Stellar smart contract development (Rust, soroban-sdk). Covers project setup, contract anatomy, storage/TTL, authorization, cross-contract calls, events, errors, upgrades, and comprehensive testing strategies.
dapp
Stellar dApp / frontend development. Covers javascript stellar-sdk, Stellar Wallets Kit, and the agentic kit data layer — useStellarData(), useContract(), useStellarWallet(). No raw RPC or curl.
stellar-mcp
MCP (Model Context Protocol) tools for Stellar development. Gives Claude direct access to the Stellar blockchain, filesystem, GitHub, and Playwright through configured MCP servers. Use when querying chain data, deploying contracts, managing repos, or running e2e tests from within the agent.