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/demogit clone --depth 1 https://github.com/omermaksutii/RugProofWrote 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/commands/omermaksutii/rugproof/demo)<a href="https://agentmods.dev/commands/omermaksutii/rugproof/demo"><img src="https://agentmods.dev/badge/commands/omermaksutii/rugproof/demo.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.00506 |
| Opus 5 | $0.00008 | $0.00253 |
| Sonnet 5 | $0.00003 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
demo 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 5d 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.
What it actually says
/demo — run on bundled vulnerable contracts
First-run experience. Lets a new user see Rugproof's output on a real (but safe) vulnerable contract — no need to bring their own code yet.
Bundled demos
Located in examples/ (Solidity) and examples-vyper/ (Vyper):
| Demo | Contract | Primary vuln class |
|---|---|---|
reentrancy |
examples/VulnerableVault.sol |
reentrancy + access-control |
oracle |
examples/SpotOracleLending.sol |
oracle-manipulation + flash-loan |
flash-loan |
examples/FlashLoanGovernance.sol |
governance flash-loan |
inflation |
examples/Inflatable4626.sol |
ERC-4626 donation attack |
replay |
examples/ReplayableBridge.sol |
signature replay (cross-chain) |
vyper |
examples-vyper/VulnerableVyper.vy |
Vyper 0.2.15 @nonreentrant miscompile + access-control |
Procedure
- Map
$ARGUMENTSto one or more demo files. Default =all. - Run
/auditon each. - Show full output (findings + grade + trust report).
- For each finding, optionally also run
/exploitto generate a working PoC. - End with a teaser:
That's what Rugproof finds on these demos.
Try it on your own code:
/audit <your-file>
/audit (scans your whole repo)
Got a deployed contract? Try:
/audit-live <chain> <addr>
Notes
- This is the marketing surface. Make the output look great — proper colors, no broken Markdown, satisfying summary.
- The 5 bundled demos should be selected such that they exhibit the most "wow" findings (visible reentrancy, oracle manip, inflation attack).
- For onboarding flows (
/rugproof-initafter-test-run), default to/demo reentrancy— quickest to read.
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.
- 5d ago First seen · 47 lines · 16 tokens per session scan A 85d53c906103
demo is a command published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 506 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.
verify-e2e-flow
Verify that the E2E scripts for the specified chain follow the documented transaction flow.
keygen-wallet
Keygen Wallet operates offline as a cold wallet. It generates keys, creates multisig addresses, and provides the first signature for multisig transactions.
watch-wallet
Watch Wallet operates online and manages public keys only. It creates unsigned transactions, sends signed transactions, and monitors transaction status.