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/cassler/awesome-claude-code-setup/pre-deploy-checkgit clone --depth 1 https://github.com/cassler/awesome-claude-code-setupWrote 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.
[](https://agentmods.dev/commands/cassler/awesome-claude-code-setup/pre-deploy-check)<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>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.00000 | $0.01028 |
| Opus 5 | $0.00000 | $0.00514 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
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.
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
-
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\\." -
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" -
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" -
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 -
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 -
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"
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.
- 4d ago First seen · 149 lines · 0 tokens per session scan A b5184d1feff3
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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.