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/kid-sid/claude-spellbook/deploy-checkgit clone --depth 1 https://github.com/kid-sid/claude-spellbookWrote 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/kid-sid/claude-spellbook/deploy-check)<a href="https://agentmods.dev/commands/kid-sid/claude-spellbook/deploy-check"><img src="https://agentmods.dev/badge/commands/kid-sid/claude-spellbook/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.00754 |
| Opus 5 | $0.00000 | $0.00377 |
| Sonnet 5 | $0.00000 | $0.00151 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a pre-deployment verification checklist before releasing to production.
Instructions
-
Determine the deployment context:
- What environment? (staging / production)
- What type of change? (feature / bugfix / hotfix / infrastructure)
- What services are affected?
-
Run through the pre-deployment checklist:
Code Readiness
- All CI checks passing on the branch/tag being deployed
- Code has been reviewed and approved (check PR status with
gh pr view) - No TODO/FIXME/HACK comments in changed files related to this deploy
- No debug code left in (console.log, print statements, debugger)
- Feature flags in place for risky changes
Testing
- Unit tests passing (
make testor equivalent) - Integration tests passing
- Manual QA completed for user-facing changes
- Load/performance test results reviewed (for high-traffic changes)
- Rollback tested or rollback plan documented
Database
- Migrations are backward-compatible (can old code run with new schema?)
- Migration has been tested against a production-size dataset
- No destructive migrations (DROP TABLE, DROP COLUMN) without data backup
- Indexes added for new queries on large tables
- Seed data / backfill scripts ready if needed
Configuration & Secrets
- Environment variables set in target environment
- Secrets rotated if compromised or newly required
- Feature flags configured for target environment
- No hardcoded environment-specific values in code
Infrastructure
- Sufficient capacity (CPU, memory, disk) for the deployment
- Health check endpoints working (
/health/live,/health/ready) - Monitoring and alerting configured for new endpoints/services
- Log aggregation capturing new log events
Communication
- Team notified of deployment window
- Stakeholders informed of new features / changes
- Runbook updated if operational procedures changed
- On-call aware of the deployment
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 · 95 lines · 0 tokens per session scan A 5332286bb20e
deploy-check is a command published in the GitHub repository kid-sid/claude-spellbook (187 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 754 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
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
ship
Deliver the increment. Then go live with a rollback you have run.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
release-tag
Create and push a version tag after a release PR has been merged.
release
Orchestrate a complete release workflow with quality gates, version bumping, and publishing automation.