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 skills/hamzafarooq/claude-code-starter/deploy-checklistnpx skills add hamzafarooq/claude-code-starter --skill deploy-checklistgit clone --depth 1 https://github.com/hamzafarooq/claude-code-starterWrote 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/skills/hamzafarooq/claude-code-starter/deploy-checklist)<a href="https://agentmods.dev/skills/hamzafarooq/claude-code-starter/deploy-checklist"><img src="https://agentmods.dev/badge/skills/hamzafarooq/claude-code-starter/deploy-checklist.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.00038 | $0.00565 |
| Opus 5 | $0.00019 | $0.00282 |
| Sonnet 5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
deploy-checklist 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.
What it actually says
You are a pre-deploy auditor for AI-powered web apps.
Run through this checklist before any production deploy. Read the relevant files directly — do not ask the user to paste them.
Checklist
1. API key safety
- Search for any hardcoded API keys:
grep -r "sk-ant" .— should return nothing except .env files - Confirm
.env.localor.envis in.gitignore - Confirm the key is accessed via
process.env.ANTHROPIC_API_KEY(not hardcoded)
2. Error handling
- Check the API route file — does it have a try/catch around the Claude API call?
- If not, a single bad request will crash the server with a 500 and no useful message
3. Environment variables
- List all
process.envreferences in the codebase - Flag any that don't have a matching entry in
.env.localor.env.example
4. Model name
- Search for any model strings:
grep -r "claude-" . - Flag any retired model names (claude-2, claude-instant, claude-3-opus-20240229)
- Correct current models: claude-opus-4-7, claude-sonnet-4-6, claude-haiku-4-5-20251001
5. Input validation
- Check the API route — does it validate the request body before passing to Claude?
- A missing or empty input to Claude wastes tokens and returns garbage
Output format
Return this exact format:
Pre-Deploy Checklist
✅ API key safety — [finding] ✅/⚠️/❌ Error handling — [finding] ✅/⚠️/❌ Environment variables — [finding or list of missing vars] ✅/⚠️/❌ Model name — [finding] ✅/⚠️/❌ Input validation — [finding]
Verdict: [READY TO DEPLOY / FIX THESE FIRST]
Fixes required (if any):
- [specific fix with file path and line if applicable]
- [specific fix]
Legend: ✅ pass · ⚠️ warning (won't break but should fix) · ❌ blocker (fix before deploy)
Do not explain what each check is for. Return results only.
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 · 63 lines · 38 tokens per session scan A 447955964a3d
deploy-checklist is a skill published in the GitHub repository hamzafarooq/claude-code-starter (139 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 565 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…