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/versoxbt/claude-initial-setup/deploy-checkgit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWhat 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.00005 | $0.00514 |
| Opus 5 | $0.00003 | $0.00257 |
| Sonnet 5 | $0.00001 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
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 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.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Check
Run a comprehensive pre-deployment verification to ensure the application is ready for release.
Steps
-
Run the full test suite:
- Execute all unit, integration, and E2E tests.
- Verify zero test failures.
- Check test coverage meets the 80% threshold.
- If any tests fail, stop and fix them before proceeding.
-
Verify the build:
- Run a clean production build.
- Check for build warnings that may indicate issues.
- Verify the build output size is reasonable (no unexpected bloat).
- Confirm no development-only code is included in the production bundle.
-
Check environment configuration:
- Verify all required environment variables are documented.
- Confirm no hardcoded development URLs, ports, or credentials exist.
- Check that environment-specific settings (database URLs, API endpoints) use env vars.
- Verify
.env.exampleis up to date with all required variables.
-
Review database migrations:
- Check that all pending migrations are included.
- Verify migrations are reversible (have a rollback path).
- Confirm migrations do not drop columns or tables without a data migration plan.
- Test migrations against a copy of production data if possible.
-
Security verification:
- No hardcoded secrets in the codebase.
- All dependencies audited (
npm audit,pip audit, etc.). - HTTPS enforced for all external communication.
- Authentication and authorization working correctly.
-
Check CI pipeline:
- Verify all CI checks are passing.
- Confirm the deployment pipeline is configured for the target environment.
- Review any skipped or ignored checks.
-
Review recent changes:
- Run
git logto review all commits since last deployment. - Verify no debugging code, console.log statements, or TODO hacks are present.
- Confirm all PRs have been reviewed and approved.
- Run
-
Create a rollback plan:
- Document the current deployed version or commit hash.
- Verify the rollback procedure works.
- Identify monitoring metrics to watch after 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.
- 2d ago First seen · 65 lines · 5 tokens per session scan A 2389d0582c43
deploy-check is a command published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 5 tokens to every session and 514 once invoked, about $0.0000 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 commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.