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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.01105 |
| Opus 5.5 | $0.00015 | $0.00442 |
| Sonnet 5.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 1mo 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.
- 1mo 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 5mo ago), licensed MIT. It adds 37 tokens to every session and 1,105 once invoked, about $0.0001 per session on Opus 5.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
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.