What is deploy-check?

A pre-deployment checklist for Cloudflare Workers projects. It checks code compilation, configuration, secrets, bindings, and cloud resources before a release.

Use it before deploying to verify TypeScript, wrangler.jsonc, OAuth and API secrets, Vectorize indexes, KV namespaces, R2 buckets, D1 databases, and other bindings.

It helps catch missing settings, secrets, resources, or migrations before they cause a failed deployment.

deploy-check — Command for Claude Code by superbenefit: A pre-deployment checklist for Cloudflare Workers projects.

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/superbenefit/sb-marketplace/deploy-check

Clone the repo

git clone --depth 1 https://github.com/superbenefit/sb-marketplace

Made for: Claude Code.

Or install cloudflare-dev, the plugin that ships this one along with the rest of its 1 skill, 4 commands, 3 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/superbenefit/sb-marketplace/deploy-check.svg)](https://agentmods.dev/commands/superbenefit/sb-marketplace/deploy-check)

Your own site

<a href="https://agentmods.dev/commands/superbenefit/sb-marketplace/deploy-check"><img src="https://agentmods.dev/badge/commands/superbenefit/sb-marketplace/deploy-check.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 443 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.1	$0.00012	$0.00443
Opus 5	$0.00006	$0.00221
Sonnet 5	$0.00002	$0.00089
Haiku 4.5	$0.00001	$0.00044

Measured 6d ago against content hash 344ea36c7aab, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

deploy-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 6d 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.

cloudflare-dev/commands/deploy-check.md · 81 lines

What it actually says

Pre-Deployment Checklist

Run through all deployment prerequisites before pushing to production.

Checks

1. TypeScript Compilation

npm run typecheck

All type errors must be resolved before deploying.

2. Configuration Validation

Verify wrangler.jsonc:

compatibility_date is current and intentional
compatibility_flags includes "nodejs_compat"
observability: { "enabled": true } is set
migrations block is correct (includes all DO/Agent classes in new_sqlite_classes)
All bindings reference valid resources

3. Secrets Verification

npx wrangler secret list

Verify all required secrets are set. Cross-reference with:

Environment variables referenced in code (env.SECRET_NAME)
OAuth configuration (client IDs, client secrets)
API keys for external services

4. Resource Verification

Vectorize indexes (if used):

npx wrangler vectorize list

Verify indexes exist with correct dimensions and metrics
Verify metadata indexes are created

KV namespaces (if used):

npx wrangler kv namespace list

R2 buckets (if used):

npx wrangler r2 bucket list

D1 databases (if used):

npx wrangler d1 list

5. Local Testing

MCP Inspector test passes (/test-mcp)
Key functionality verified locally
Error handling tested

6. Deploy

If all checks pass:

npm run deploy

Usage

/deploy-check $ARGUMENTS

$ARGUMENTS optionally limits scope. Examples:

/deploy-check - Full checklist
/deploy-check secrets - Only check secrets
/deploy-check resources - Only verify cloud resources

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.

6d ago First seen · 81 lines · 12 tokens per session scan A 344ea36c7aab

Subscribe to this mod's changes

deploy-check is a command published in the GitHub repository superbenefit/sb-marketplace (5 stars, last pushed 7mo ago), licensed CC0-1.0. It adds 12 tokens to every session and 443 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.

CI and CD Cloud DevOps and cloud

deploy-check