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/auditgit 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/audit)<a href="https://agentmods.dev/commands/omermaksutii/rugproof/audit"><img src="https://agentmods.dev/badge/commands/omermaksutii/rugproof/audit.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.00035 | $0.01595 |
| Opus 5 | $0.00017 | $0.00797 |
| Sonnet 5 | $0.00007 | $0.00319 |
| Haiku 4.5 | $0.00003 | $0.00160 |
Grade A, and why
audit 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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit — full security audit
You are conducting a thorough smart contract security audit. Be rigorous; be skeptical. Treat every line of state-mutating code as if an adversary will read it after you do.
Target
$ARGUMENTS — if empty, default to the include/exclude globs from .rugproof.yml at the repo root (fall back to src/**/*.sol contracts/**/*.sol if no config).
Procedure
Step 1 — Inventory the target
- Read the target file(s) and any directly imported files in-repo.
- Identify the protocol type. Look for tell-tales:
- ERC-20 + Pair/Pool/Factory → AMM (V2/V3/V4)
- cToken/aToken/lToken,
LendingPool,comptroller,liquidate→ lending stake+rewards+ checkpoints → stakingmint/burnwith cross-chain Merkle / sigs → bridge- Governor / Timelock / proposal → governance
- ERC-4626 / vault / strategies → yield aggregator
- ERC-721 / ERC-1155 / royalties → NFT
- Detect language: Solidity, Vyper, Yul/assembly-heavy, Rust (Stylus/CosmWasm/Anchor).
- Identify Solidity version. Note version-specific risks (PUSH0, EIP-6780, etc.).
Step 2 — Auto-invoke vuln skills
The skills/ library auto-loads based on code patterns. Verify you've covered the relevant categories:
reentrancy · access-control · oracle-manipulation · flash-loan-attacks · mev-frontrunning · signature-replay · storage-layout · initialization · unchecked-calls · dos-vectors · integer-issues · delegatecall-risks · tx-context-misuse · token-compatibility · approval-issues · selfdestruct-eip6780 · inline-assembly · pragma-and-addresses · centralization-risk · permit2-patterns · erc1271-contract-signatures · diamond-eip2535 · erc4626-inflation · erc4337-account-abstraction · cross-chain-messaging · restaking-eigenlayer · intents-erc7683 · vyper-specific · ve-lock-governance · fee-on-transfer · signature-malleability · mev-pbs · liquidation-cascade · oracle-redundancy · cross-contract-state · zk-verifier-bugs
For each that matches code in the target, produce findings.
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.
- 4d ago First seen · 123 lines · 35 tokens per session scan A f777cb94fdac
audit is a command published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,595 once invoked, about $0.0002 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.
codespace-verify
Command "codespace-verify" from kota1026/quantum-shield, covering codespaces ui確認コマンド, 1. codespaces起動確認, サービス起動状態確認, postgresql, redis, rabbitmqが起動していない場合 and フロントエンド起動.
pr-merge
Command "pr-merge" from kota1026/quantum-shield, covering pr作成・マージコマンド, 1. 変更確認, 2. コミット（未コミットがある場合）, 3. pr作成 and 4. マージ.
balance
Show native + ERC-20 token balances (with USD) for a wallet.
setup
Connect and select an Alchemy app for this session.