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 agentmods add commands/omermaksutii/rugproof/exploitgit clone --depth 1 https://github.com/omermaksutii/RugProofWhat 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 | $0.00018 | $0.00941 |
| Opus 5 | $0.00009 | $0.00470 |
| Sonnet 5 | $0.00004 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
exploit 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/exploit — write a working PoC
This is the headline feature. For a given finding ID, produce a Foundry test that:
- Sets up the vulnerable state.
- Executes the exploit.
- Asserts the attacker gained value or the protocol was broken.
- Compiles.
- The test passes when run.
If --story is set, also produce a narrative "attack walkthrough" — punchy prose suitable for a tweet thread or blog post.
Procedure
Step 1 — Read the finding and the target
- Pull finding
$ARGUMENTS[0]from the latest audit. - Read the affected file and all imports it needs.
- Note the function signatures, state vars, and any setup needed (e.g. funded balances, deployed dependencies like a Uniswap V2 pair).
Step 2 — Dispatch exploit-poc-writer subagent
The subagent writes the Foundry test. Use Foundry's Test base + vm.prank, vm.deal, vm.warp, vm.expectRevert, vm.startPrank, etc.
Structure:
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;
import "forge-std/Test.sol";
import {Vault} from "src/Vault.sol";
import {MaliciousReceiver} from "./MaliciousReceiver.sol";
contract ExploitREENT001 is Test {
Vault vault;
address attacker = makeAddr("attacker");
address victim = makeAddr("victim");
function setUp() public {
vault = new Vault();
vm.deal(victim, 10 ether);
vm.deal(attacker, 1 ether);
vm.prank(victim);
vault.deposit{value: 10 ether}();
}
function test_Reentrancy_Drain() public {
MaliciousReceiver bad = new MaliciousReceiver(vault);
vm.deal(address(bad), 1 ether);
vm.startPrank(attacker);
bad.attack{value: 1 ether}(); // ← seed deposit + trigger reentrancy
assertGt(address(bad).balance, 1 ether, "exploit failed to drain");
assertLt(address(vault).balance, 1 ether, "vault not drained");
}
}
Plus any auxiliary attacker contract.
Step 3 — Compile and run
Use the forge-runner MCP:
mcp__forge-runner__build()
mcp__forge-runner__test(test="test_Reentrancy_Drain")
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.
- 2d ago First seen · 106 lines · 18 tokens per session scan A dee25e8efcb7
exploit is a command published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 941 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
krait-fuzz
Run an invariant-based fuzzing campaign: Understand → Extract Invariants → Generate Foundry Tests → Run & Fix Iteratively → Report.
krait-poc
Write and run a valid Foundry proof-of-concept that proves (or disproves) a Solidity exploit by asserting the actual harm on a forked chain or against local source.
krait-quick
Run a streamlined audit: Recon → Detection → Verification → Report. Skips state inconsistency analysis and cross-feed iteration for speed.
fix-btc-e2e-p11
Fix errors in BTC E2E test (Pattern 11: P2TR Tapscript M-of-N).
fix-btc-e2e-p4
Fix errors in BTC E2E test (Pattern 4: P2SH-P2WSH 2-of-3 Multisig).
fix-btc-e2e-p6
Fix errors in BTC E2E test (Pattern 6: P2WSH 2-of-3 Multisig).