Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rafaelkamimura/claude-toolsnpx agentmods add commands/rafaelkamimura/claude-tools/deployWrote 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/rafaelkamimura/claude-tools/deploy)<a href="https://agentmods.dev/commands/rafaelkamimura/claude-tools/deploy"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/deploy/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/commands/rafaelkamimura/claude-tools/deploy"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/deploy.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.00000 | $0.02863 |
| Opus 5.5 | $0.00000 | $0.01145 |
| Sonnet 5.5 | $0.00000 | $0.00573 |
| Haiku 4.5 | $0.00000 | $0.00286 |
Grade A, and why
deploy scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -f $BLUE_URL/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Deployment Manager
Environment-aware deployment orchestrator with support for multiple strategies, automatic rollback, and health monitoring.
Purpose
- Deploy to dev/staging/production environments
- Support blue-green and canary deployments
- Automatic rollback on failure
- Health checks and smoke tests
- Container and serverless deployment
Workflow
Step 1: Environment Selection
-
STOP → "Select deployment target:"
1. Development - Local/dev environment 2. Staging - Pre-production testing 3. Production - Live environment 4. Custom - Specify environment Choose environment (1-4): -
Deployment Strategy
- STOP → "Select deployment strategy:"
1. Rolling update - Gradual replacement 2. Blue-green - Instant switchover 3. Canary - Percentage-based rollout 4. Recreate - Stop old, start new 5. Feature flag - Toggle-based Choose strategy (1-5): -
Deployment Options
- STOP → "Run pre-deployment tests? (y/n):"
- STOP → "Enable automatic rollback? (y/n):"
- STOP → "Send deployment notifications? (y/n):"
Step 2: Pre-Deployment Checks
-
Verify Build
# Check if build exists if [ ! -f "dist/index.js" ] && [ ! -d "build" ]; then echo "No build found. Running build..." npm run build || make build || cargo build --release fi -
Run Tests
# Critical tests only npm run test:smoke || pytest tests/smoke || go test ./tests/smoke -
Check Dependencies
# Verify all dependencies are installed npm ci --production || pip install -r requirements.txt --no-dev -
Security Scan
# Quick security check npm audit --production || safety check
Step 3: Container Deployment
- Build Docker Image
# Build with version tag VERSION=$(git describe --tags --always) docker build -t myapp:$VERSION . docker tag myapp:$VERSION myapp:latest
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 · 492 lines · 0 tokens per session scan A 54c15b00b5b5
deploy is a command published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,863 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.