pre-deploy-check

pre-deploy-check is a command for coding agents from cassler/awesome-claude-code-setup. It costs 0 tokens per session (1,028 once invoked), scanned A, original, MIT.

A checklist for deciding whether a project is ready to deploy to an environment such as production. Deployment means releasing the code so people or other systems can use it.

In plain words
What is it for?
Use it to check environment variables, development URLs, secret files, file permissions, security issues, builds and deployment configuration.
Why use it?
It catches debug code, unsafe settings, exposed secrets, missing configuration, build failures and other release risks.

Command

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/cassler/awesome-claude-code-setup/pre-deploy-check
Clone the repo
git clone --depth 1 https://github.com/cassler/awesome-claude-code-setup

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.

agentmods badge for pre-deploy-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/pre-deploy-check.svg)](https://agentmods.dev/commands/cassler/awesome-claude-code-setup/pre-deploy-check)
Your own site
<a href="https://agentmods.dev/commands/cassler/awesome-claude-code-setup/pre-deploy-check"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/pre-deploy-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,028 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.00000 $0.01028
Opus 5 $0.00000 $0.00514
Sonnet 5 $0.00000 $0.00206
Haiku 4.5 $0.00000 $0.00103

Measured 4d ago against content hash b5184d1feff3, 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-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 4d 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-check.md · 149 lines

How it starts

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

Pre-Deployment Checklist

Please help me ensure we're ready to deploy to ${ENVIRONMENT:-production}.

Deployment type: ${DEPLOY_TYPE:-standard} Target branch: ${TARGET_BRANCH:-main} Skip checks: ${SKIP_CHECKS:-none}

Critical Checks

  1. Remove debug code:

    # Check for console logs
    ch cq console-logs
    
    # Find debug flags
    chs find-code "DEBUG|debug.*=.*true|__DEV__"
    
    # Check for development URLs
    chs find-code "localhost|127\\.0\\.0\\.1|192\\.168\\."
    
  2. Environment configuration:

    # Find environment variables
    chs find-code "process\\.env\\.|ENV\\[|getenv\\("
    
    # Check for missing defaults
    chs find-code "process\\.env\\.\\w+" 2>/dev/null | while IFS= read -r match; do
      echo "$match" | grep -q "||" || echo "Missing default: $match"
    done
    
    # Verify .env.example is updated
    diff .env .env.example 2>/dev/null || echo "Check .env files"
    
  3. Security scan:

    # Final secrets check
    ch cq secrets-scan
    
    # Check file permissions
    find . -type f -name "*.${SCRIPT_EXT:-sh|py}" -exec ls -la {} \; | grep -v "r--"
    
    # Verify no sensitive files
    chs find-file "*.pem|*.key|*.env|*.secret"
    
  4. Build verification:

    # Clean build
    # Remove any build artifacts (adjust paths for your project)
    # Examples: dist/, build/, target/, out/, _site/
    
    # Run your project's build command
    # Examples: npm run build, make build, gradle build, etc.
    
    # Verify no source maps or debug files in production
    # Check your build output directory for .map files or debug symbols
    
  5. Test suite:

    # Run your project's test suite
    # Examples: npm test, pytest, go test, mvn test, etc.
    
    # Run E2E/integration tests if available
    
    # Check test coverage if configured
    
  6. Database checks:

    # Find migration files
    chs find-file "*migration*|*migrate*" --sort-date | tail -5
    
    # Check for migration conflicts
    git diff "${TARGET_BRANCH:-main}" --name-only | grep -i migration
    
    # Look for schema changes
    chs find-code "CREATE TABLE|ALTER TABLE|DROP TABLE"
    

Read the full file on GitHub · 149 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. 4d ago First seen · 149 lines · 0 tokens per session scan A b5184d1feff3

Subscribe to this mod's changes

pre-deploy-check is a command published in the GitHub repository cassler/awesome-claude-code-setup (267 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,028 tokens. 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-30.