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-poc-foundrygit 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-poc-foundry)<a href="https://agentmods.dev/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-poc-foundry"><img src="https://agentmods.dev/badge/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-poc-foundry/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-poc-foundry"><img src="https://agentmods.dev/badge/skills/olaradiallysymmetrical491/web3-bug-bounty-hunting-ai-skills/web3-poc-foundry.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.09368 |
| Opus 5 | $0.00030 | $0.04684 |
| Sonnet 5 | $0.00012 | $0.01874 |
| Haiku 4.5 | $0.00006 | $0.00937 |
Grade A, and why
web3-poc-foundry 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-poc-foundry — 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 — 1,137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PoC WRITING + FOUNDRY COMPLETE REFERENCE
Immunefi requires RUNNABLE code. Not pseudocode. Not steps. Running Foundry tests with before/after logs and a passing assert.
QUICK START
# Immunefi official templates (preferred for submissions)
forge init my-poc --template immunefi-team/forge-poc-templates --branch default
forge init my-poc --template immunefi-team/forge-poc-templates --branch reentrancy
forge init my-poc --template immunefi-team/forge-poc-templates --branch flash_loan
forge init my-poc --template immunefi-team/forge-poc-templates --branch price_manipulation
# Or blank Foundry project
forge init my-poc
cd my-poc
# Setup .env
echo "MAINNET_RPC_URL=https://eth.llamarpc.com" > .env
echo "BASE_RPC_URL=https://base.llamarpc.com" >> .env
echo "ARB_RPC_URL=https://arb1.arbitrum.io/rpc" >> .env
# Run exploit
source .env
forge test --match-test testExploit -vvvv --fork-url $MAINNET_RPC_URL
STANDARD PoC TEMPLATE (Production Quality for Immunefi)
// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.10;
import "forge-std/Test.sol";
import "forge-std/console.sol";
/**
* @title [Protocol Name] - [Bug Description]
* @notice PoC for Immunefi submission
* @dev Demonstrates [impact] by exploiting [root cause]
*
* Vulnerable contract: [address] ([name])
* Vulnerable function: [functionName]
* Immunefi program: [URL]
* Severity: [Critical/High/Medium/Low]
*/
// Minimal interfaces — only what you need
interface IVulnProtocol {
function deposit(uint256 amount) external;
function withdraw(uint256 amount) external;
function balanceOf(address) external view returns (uint256);
}
interface IERC20 {
function approve(address, uint256) external returns (bool);
function balanceOf(address) external view returns (uint256);
function transfer(address, uint256) external returns (bool);
function transferFrom(address, address, uint256) external returns (bool);
}
contract ExploitPoC is Test {
// ============================================================
// CONFIGURATION
// ============================================================
uint256 constant ATTACK_BLOCK = 18_000_000; // pin block for reproducibility
address constant VULN_CONTRACT = 0x...;
address constant TOKEN = 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48; // USDC
IVulnProtocol vuln = IVulnProtocol(VULN_CONTRACT);
IERC20 token = IERC20(TOKEN);
// ============================================================
// SETUP
// ============================================================
function setUp() public {
vm.createSelectFork(vm.envString("MAINNET_RPC_URL"), ATTACK_BLOCK);
vm.label(VULN_CONTRACT, "VulnerableProtocol");
vm.label(TOKEN, "USDC");
vm.label(address(this), "Attacker");
}
// ============================================================
// EXPLOIT
// ============================================================
function testExploit() public {
uint256 attackerBefore = token.balanceOf(address(this));
uint256 protocolBefore = token.balanceOf(VULN_CONTRACT);
console.log("=== INITIAL STATE ===");
console.log("Attacker USDC: ", attackerBefore);
console.log("Protocol USDC: ", protocolBefore);
console.log("--------------------");
// Step 1: [description]
deal(TOKEN, address(this), 1e6); // 1 USDC starting capital
// Step 2: [description]
token.approve(VULN_CONTRACT, type(uint256).max);
vuln.deposit(1e6);
// Step 3: [the exploit]
// ... exploit logic ...
uint256 attackerAfter = token.balanceOf(address(this));
uint256 protocolAfter = token.balanceOf(VULN_CONTRACT);
console.log("=== FINAL STATE ===");
console.log("Attacker USDC: ", attackerAfter);
console.log("Protocol USDC: ", protocolAfter);
console.log("Profit: ", attackerAfter - attackerBefore);
console.log("Protocol loss: ", protocolBefore - protocolAfter);
assertGt(attackerAfter, attackerBefore, "Exploit failed: no profit");
}
}
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 · 1,137 lines · 59 tokens per session scan A 90e19fd0ff0c
web3-poc-foundry 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 9,368 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-poc-foundry, 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.