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-hunt-foundationgit 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-hunt-foundation)<a href="https://agentmods.dev/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-hunt-foundation"><img src="https://agentmods.dev/badge/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-hunt-foundation/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-hunt-foundation"><img src="https://agentmods.dev/badge/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-hunt-foundation.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.00042 | $0.02512 |
| Opus 5 | $0.00021 | $0.01256 |
| Sonnet 5 | $0.00008 | $0.00502 |
| Haiku 4.5 | $0.00004 | $0.00251 |
Grade A, and why
web3-hunt-foundation 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-hunt-foundation — 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WEB3 HUNT FOUNDATION
Mindset + Recon + Setup. Read this before touching any new target's code. Replaces: 01-mindset, 02-recon-setup, 20-chain-complete
PART 1: THE HUNTER MINDSET
The Core Mental Shift
You are NOT looking for "vulnerabilities" in the abstract. You are looking for specific actions an attacker can take TODAY that result in profit.
Everything flows from one question: "What can I STEAL, FREEZE, or DESTROY — and what do I END UP WITH?"
The Bug Validation Template
Apply to every finding before writing a single line:
I am an attacker. I will:
1. SETUP: What do I need? (wallet, capital, any whitelisted permissions?)
2. CALL: Exact transactions, exact order, exact function names
3. RESULT: What do I end up with that I didn't start with?
4. COST: Gas + capital + flash loan fee + any other expense
5. DETECT: Can anyone stop or reverse this?
6. NET ROI: I gained X at cost of Y. Is Y << X?
If you can't fill in steps 2 and 3 with specific function calls → it's not a real bug. Stop. Move on.
10 Attacker Questions (Ask For Every External Function)
- What if
amount = 0? Does anything revert or silently pass? - What if I call this function twice in the same block?
- What if I call this before
initialize()is called? - What if I front-run this transaction?
- What if the external call fails? Does state get half-updated?
- What if the token has fee-on-transfer? Does
amount received ≠ amount sent? - What if I pass
address(0)or a malicious contract as an address param? - What if I pass
type(uint256).maxas a numeric param? - Can I combine this with a flash loan? (zero-cost capital changes the math)
- Does a sibling function lack the same modifier this function has?
Question #10 explains 19% of all Critical findings. If
vote()hasonlyRole(VOTER), checkpoke(),reset(),harvest()— the missing modifier on the sibling IS the bug.
6 Triager Counter-Questions (Disprove Your Own Finding)
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 · 284 lines · 42 tokens per session scan A c37b59108722
web3-hunt-foundation is a skill published in the GitHub repository Olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills (5 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 2,512 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to web3-hunt-foundation, 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.