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/viknesh20-20/claude-code-tool-kit/deploy-checklistnpx skills add viknesh20-20/claude-code-tool-kit --skill deploy-checklistgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/deploy-checklist)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/deploy-checklist"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/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.00037 | $0.01105 |
| Opus 5 | $0.00018 | $0.00553 |
| Sonnet 5 | $0.00007 | $0.00221 |
| Haiku 4.5 | $0.00004 | $0.00111 |
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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Deployment Checklist
Current State
!git branch --show-current 2>/dev/null
!git log --oneline -10 2>/dev/null
!git status --short 2>/dev/null
Verification Checklist
Go through each section. Mark items as PASS, FAIL, WARN, or N/A.
1. Code Readiness
- All changes are committed — no uncommitted work
- Branch is up to date with main/master
- No merge conflicts
- All PRs for this release are merged
- No draft PRs accidentally included
2. Testing
- All unit tests pass
- All integration tests pass
- End-to-end tests pass (if applicable)
- No new test failures compared to main branch
- Edge cases for new features are tested
- Performance-sensitive changes have been load tested
3. Code Quality
- No
console.log/print/ debug statements left in - No
TODOorFIXMEcomments that should be resolved - No commented-out code blocks
- Linting passes with zero errors
- Type checking passes (if applicable)
4. Security
- No hardcoded secrets, tokens, or API keys
- No new dependencies with known vulnerabilities
- Input validation in place for new endpoints
- Authentication/authorization checked for new routes
- CORS configuration is correct for the target environment
5. Database & Migrations
- All migrations are created and tested
- Migrations are backwards compatible (can rollback)
- No destructive migrations without data backup plan
- Indexes added for new queries
- Migration order is correct
6. Configuration & Environment
- All new environment variables are documented
- Environment variables are set in target environment
- Feature flags are configured correctly
- Third-party service configs are updated (if needed)
- SSL/TLS certificates are valid
7. API & Breaking Changes
- No breaking API changes without versioning
- API documentation is updated
- Deprecation notices added for removed features
- Consumers (frontend, mobile, third-party) are notified
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 · 121 lines · 37 tokens per session scan A 376036956fb3
deploy-checklist is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 1,105 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-31.
Other skills, from other repositories
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…
suede-aso
Suede-owned app-store optimization discipline for keyword fields, titles, subtitles, descriptions, screenshots, ratings context, and competitor listing audits. Use when improving App Store or Google Play visibility or listing conversion from a live app URL and current console evidence. NOT FOR: building or releasing…
suede-copy
Suede Labs conversion-copy writer: landing sections, email, microcopy, buttons, headlines, CTAs, variants, and anti-slop edits. Use when asked to write or rewrite conversion copy for one surface in one pass — a hero, a button set, an email subject, a README section, a product blurb — or when copy on a single surface…
copywriting
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value…