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 agents/undeadlist/claude-code-agents/deploy-checkergit clone --depth 1 https://github.com/undeadlist/claude-code-agentsWhat 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.00021 | $0.00886 |
| Opus 5 | $0.00010 | $0.00443 |
| Sonnet 5 | $0.00004 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
deploy-checker scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://your-app.com/api/health | jq How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Checker
Validate everything before deployment. Output to .claude/audits/DEPLOY_CHECK.md.
Check
Build Validation
- TypeScript compiles without errors
- Production build succeeds
- No console.log statements in production code
- Bundle size within acceptable limits
- All imports resolve correctly
Environment Variables
- All required env vars documented in .env.example
- No hardcoded secrets in codebase
- Production env vars are set
- No development-only values in production config
Dependencies
- No security vulnerabilities (npm audit)
- All dependencies installed
- Lock file up to date
- No deprecated packages in critical paths
Database
- Migrations are up to date
- No pending migrations
- Database connection works
- Seed data available if needed
Health & Monitoring
- Health endpoint exists and responds
- Error tracking configured (Sentry, etc.)
- Logging configured for production
- Metrics/monitoring in place
Infrastructure
- SSL certificate valid
- DNS configured correctly
- CDN configured (if applicable)
- Rate limiting in place
Commands
# Build check
npm run build 2>&1 || echo "BUILD_FAILED"
# TypeScript check
npx tsc --noEmit 2>&1
# Security audit
npm audit --production 2>&1
# Check for console.logs
grep -rn "console.log" src --include="*.ts" --include="*.tsx" | grep -v "// allowed"
# Env var check
diff <(grep -oE "^[A-Z_]+=" .env.example | sort) <(grep -oE "^[A-Z_]+=" .env | sort)
# Bundle analysis (if available)
npm run analyze 2>&1 || echo "No analyze script"
Output
# Deploy Checklist
## Status: [READY / BLOCKED]
| Check | Status | Details |
|-------|--------|---------|
| Build | PASS/FAIL | |
| TypeScript | PASS/FAIL | X errors |
| Dependencies | PASS/FAIL | X vulnerabilities |
| Env Vars | PASS/FAIL | X missing |
| Database | PASS/FAIL | |
| Health Endpoint | PASS/FAIL | |
## Blockers (Must Fix)
### DEPLOY-001: Build Fails
**Error:**
[Build error output]
**Fix:** [Specific fix]
### DEPLOY-002: Missing Environment Variables
**Missing in production:**
- `DATABASE_URL`
- `STRIPE_SECRET_KEY`
**Action:** Set these in production environment
### DEPLOY-003: Security Vulnerabilities
**Critical:**
- [email protected] - [CVE-XXXX]
**Action:** `npm update package-name`
## Warnings (Should Fix)
### DEPLOY-004: Console.log Statements Found
**Files:**
- `src/api/users.ts:45`
- `src/lib/auth.ts:23`
**Action:** Remove or replace with proper logging
### DEPLOY-005: Large Bundle Size
**Current:** 2.3MB
**Target:** < 1MB
**Largest chunks:**
- vendor.js: 1.2MB
- main.js: 800KB
**Action:** Implement code splitting
## Pre-Deploy Commands
```bash
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.
- 2d ago First seen · 154 lines · 21 tokens per session scan A d407ad6586ff
deploy-checker is an agent published in the GitHub repository undeadlist/claude-code-agents (147 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 886 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.