quick-scan

A fast security scan for Solidity smart contracts, which are programs that run on blockchains. It checks staged contract files or a specified project for only critical and high-severity findings.

In plain words
What is it for?
Use it to look for issues such as reentrancy, missing access controls, unsafe price data, ignored call results, unsafe initialization, replayable signatures, risky delegate calls, and certain flash-loan attacks.
Why use it?
It gives a quick pre-commit check without running the broader audit process. This can catch several common contract vulnerabilities before code is committed.

Command

Part of the rugproof plugin — 35 commands, 23 agents shipped together

Install

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.

agentmods
npx agentmods add commands/omermaksutii/rugproof/quick-scan
Clone the repo
git clone --depth 1 https://github.com/omermaksutii/RugProof

Or install rugproof, the plugin that ships this one along with the rest of its 35 commands, 23 agents.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 595 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 3fa85a7ea32d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

commands/quick-scan.md · 64 lines

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

  1. Resolve target from $ARGUMENTS or staged files (git diff --cached --name-only -- '*.sol').
  2. 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,
  3. Read full function context only for matched lines.
  4. 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_threshold from .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-scan directly (not from a hook), output is the same; the exit code just isn't meaningful.

Read the full file on GitHub · 64 lines

Changes

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.

  1. 3d ago First seen · 64 lines · 18 tokens per session scan A 3fa85a7ea32d

Subscribe to this mod's changes

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.