An interactive checklist for deciding whether blockchain contracts are ready to launch. It checks operational controls, such as multisig ownership and monitoring, alongside code-safety gates.

Use it before mainnet deployment to review administration, timelocks, pausing, emergency fund recovery, proxy upgrade safety, and monitoring.

It exposes launch risks that source code alone may not reveal and produces a final GO or NO-GO decision. Items that cannot be checked automatically are presented for confirmation.

pre-deploy — Command for coding agents by omermaksutii: An interactive checklist for deciding whether blockchain contracts are…

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/pre-deploy

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.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/omermaksutii/rugproof/pre-deploy.svg)](https://agentmods.dev/commands/omermaksutii/rugproof/pre-deploy)

Your own site

<a href="https://agentmods.dev/commands/omermaksutii/rugproof/pre-deploy"><img src="https://agentmods.dev/badge/commands/omermaksutii/rugproof/pre-deploy.svg" alt="Measured on agentmods" height="20"></a>

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 961 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.

Model	Per session	Once invoked
Fable 5	$0.00033	$0.00961
Opus 5	$0.00016	$0.00481
Sonnet 5	$0.00007	$0.00192
Haiku 4.5	$0.00003	$0.00096

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

Security

Grade A, and why

pre-deploy 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/pre-deploy.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/pre-deploy — the go/no-go gate

The last command you run before mainnet. It walks every launch-readiness gate — operational (multisig, timelock, monitoring) and code (clean strict audit, upgrade safety) — asks you to confirm the ones it can't verify from source, and returns a single GO or NO-GO.

Procedure

Step 1 — Locate the deployment

$ARGUMENTS is the project/contract dir (default .). Identify the contracts being launched and whether any are proxies.

Step 2 — Walk the checklist

Go item by item. For each, verify from source/config where possible, otherwise ask the user to confirm:

Multisig owner (not EOA) — resolve owner() / admin role holder; confirm it is a Safe, not an EOA. [[centralization-risk]].
Timelock on admin functions — privileged setters routed through a timelock with a non-zero delay.
Pause / circuit-breaker — a pause() exists and is reachable by the guardian.
Emergency withdrawal path — funds recoverable if the contract is paused/bricked, without trapping users.
Upgrade safety — if any contract is a proxy, run /upgrade-safety and require it clean.
Monitoring / alerting — Forta, OZ Defender, or Tenderly alerts wired for admin events and anomalous flows.
Bug bounty live — /bounty program published before TVL arrives.
Clean strict audit — run /audit-strict; require zero unresolved High/Critical.
Verified source on explorer — source verified post-deploy (or planned in the deploy script).
Constructor args sanity — args match intended owner / fee / oracle; no placeholder addresses.
Access-control matrix documented — every role → who holds it → what it can do, written down.

Step 3 — Score each item

Mark PASS / FAIL / N-A. Any FAIL on items 1, 2, 5, or 8 forces an overall NO-GO. Dispatch the defender agent to sanity-check borderline items.

Step 4 — Output

Pre-deploy readiness: ./contracts (Vault is UUPS proxy)

   1. Multisig owner            PASS   owner = 0xSafe…ab (3/5 Safe)
   2. Timelock on admin         FAIL   setFee/setOracle are not behind the timelock
   3. Pause / circuit-breaker   PASS   pause() guarded by guardian role
   4. Emergency withdrawal      PASS   emergencyWithdraw() pull-based, no trap
   5. Upgrade safety            PASS   /upgrade-safety clean (append-only storage)
   6. Monitoring / alerting     FAIL   no Defender/Forta alerts configured
   7. Bug bounty live           N-A    launching as audited-only, bounty in 2 weeks
   8. Clean strict audit        PASS   /audit-strict: 0 High/Critical open
   9. Verified source           PASS   verification step in deploy script
  10. Constructor args sanity   PASS   owner/oracle/fee match runbook
  11. Access-control matrix      FAIL   roles undocumented

  ─────────────────────────────────────────────────────────────
  Verdict: NO-GO
  Blockers: #2 (admin not timelocked) is a hard gate.
  Before launch: route setters through the timelock, wire alerts (#6),
  and document the role matrix (#11).

Read the full file on GitHub · 68 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.

3d ago First seen · 68 lines · 33 tokens per session scan A 2796ff12c58f

Subscribe to this mod's changes

pre-deploy is a command published in the GitHub repository omermaksutii/RugProof (9 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 961 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.

Security Web3 and blockchain berachain blockchain claude-code claude-code-plugin defi ethereum

pre-deploy

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/pre-deploy — the go/no-go gate

Procedure

Step 1 — Locate the deployment

Step 2 — Walk the checklist

Step 3 — Score each item

Step 4 — Output

What this file has done since we first saw it

Other commands, from other repositories

krait-fuzz

krait-poc

krait-quick

codespace-verify

pr-merge

balance