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.
git 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/rug-check)<a href="https://agentmods.dev/commands/omermaksutii/rugproof/rug-check"><img src="https://agentmods.dev/badge/commands/omermaksutii/rugproof/rug-check.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.1 | $0.00028 | $0.00890 |
| Opus 5 | $0.00014 | $0.00445 |
| Sonnet 5 | $0.00006 | $0.00178 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
rug-check 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 7d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/rug-check — can the owner rug you?
A quick, high-signal scan for the one question every holder actually cares about: how much power does the deployer have, and can they drain, mint, freeze, or trap funds at will? Returns a single rugability score and an itemized owner-powers checklist.
Procedure
Step 1 — Resolve the target
$ARGUMENTS may be a local source file/dir or a deployed address with --chain. For a deployed token, pull live safety metadata first:
mcp__token-metadata__check_safety(chain=<c>, address=<address>)
This returns honeypot flags, tax/fee hooks, holder concentration, and LP-lock status to fold into the score.
Step 2 — Dispatch the rug specialist
Dispatch the economic-rug-specialist agent over the source. It hunts for unilateral owner powers and reads the relevant skills ([[centralization-risk]], [[access-control]]).
Step 3 — Scan owner powers
Grep + reason over each power. Each present power adds weight to the score:
grep -nE 'onlyOwner|onlyRole|_owner|hasRole' src/**/*.sol
- Drain —
withdrawAll,sweep,rescueTokens, arbitrarycall/transferof pooled funds (+25) - Mint —
mint()reachable by owner, no cap (+20) - Pause-forever —
pause()with no auto-unpause / timelock (+15) - Blacklist / freeze —
blacklist,setFrozen, transfer hooks gating addresses (+15) - Fee / reward change — owner sets
feeBps/taxBpswith no cap or to 100% (+10) - Upgradeable, no timelock — UUPS/Transparent proxy whose admin is an EOA with no delay (+20)
- Hidden owner — ownership behind assembly, a second admin role, or a delegatecall-reachable setter (+15)
Step 4 — Score and verdict
Sum weights, cap at 100. Map to a verdict:
0–29→ SAFE30–59→ CAUTION60–100→ HIGH RUG RISK
Output
Rug check: 0xToken… (base)
Rugability score: 78 / 100 → HIGH RUG RISK
Owner powers:
✗ drain pooled funds owner can call sweep(address,uint256) on any token (+25)
✗ unlimited mint mint(to,amt) is onlyOwner, no maxSupply (+20)
✗ upgradeable, no timelock UUPS admin is an EOA (0xEOA…), 0s delay (+20)
✓ pause no pause function
✗ fee change setTaxBps() uncapped — owner can set to 99% (+13)
✓ blacklist none
✓ hidden owner single visible owner, no shadow admin
Token metadata: LP not locked, top holder 41% supply, sell-tax hook present.
Verdict: HIGH RUG RISK — owner can mint, drain, and instantly upgrade. Do not LP.
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.
- 7d ago First seen · 78 lines · 28 tokens per session scan A 42a131e20dbb
rug-check is a command published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 890 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.