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/quick-scangit 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.00595 |
| Opus 5 | $0.00009 | $0.00298 |
| Sonnet 5 | $0.00004 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
quick-scan 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 3d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/quick-scan — fast triage
Lighter than /audit. Designed to run in pre-commit hooks. Targets only Critical and High findings.
What's skipped vs /audit
- No subagent dispatch (no parallel specialists).
- No exploit chains.
- No invariant pass.
- No trust report.
- No deployment fetching.
What's kept
- Auto-invoke vuln skills, but only the highest-yield ones for fast detection:
- reentrancy (CEI violations)
- access-control (missing modifiers)
- oracle-manipulation (spot-price reads)
- unchecked-calls (ignored returns)
- initialization (public init, missing _disableInitializers)
- signature-replay (missing nonces/chainId)
- delegatecall-risks (delegatecall to user input)
- flash-loan-attacks (spot-balance for vote weight, ERC-4626 inflation)
For each, regex-grep first, then read context only for matches.
Procedure
- Resolve target from
$ARGUMENTSor staged files (git diff --cached --name-only -- '*.sol'). - For each fast skill, run pattern detection:
- reentrancy → grep for
.call{value:followed by state write - access-control → grep for state-mutating externals missing modifiers
- oracle-manipulation → grep for
slot0,getReserves,latestAnswer - unchecked-calls → grep for
.call(not assigned to(bool ok,
- reentrancy → grep for
- Read full function context only for matched lines.
- Emit Critical/High findings only. Skip everything Medium and below.
Output
Compact, designed for CLI consumption:
Rugproof quick-scan
✗ Vault.sol:142 [C/REENT-001] withdraw() updates balance after external call
✗ Vault.sol:204 [H/ORACLE-001] slot0() used for collateral pricing (sandwichable)
⚠ pre-commit threshold: critical — 1 critical, 1 high found → blocking commit
Exit code:
- 0 if no findings at/above
severity_thresholdfrom.rugproof.yml - 1 if findings at/above threshold (blocks commit/push)
Notes
- Aim for <5 seconds on a small file, <30s on the whole repo.
- False positives are acceptable; false negatives are not. Quick-scan errs on side of flagging.
- If user runs
/quick-scandirectly (not from a hook), output is the same; the exit code just isn't meaningful.
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.
- 3d ago First seen · 64 lines · 18 tokens per session scan A 3fa85a7ea32d
quick-scan 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 595 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-p6
Fix errors in BTC E2E test (Pattern 6: P2WSH 2-of-3 Multisig).
phase6-start
Command "phase6-start" from kota1026/quantum-shield, covering phase 6 $arguments 開始, step 1: 進捗状況を確認, step 2: 未完了画面を特定, step 3: 必須ファイルを読み込む and step 4: インフラ確認.