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.
git clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/deploy)<a href="https://agentmods.dev/commands/xrensiu/claude-code-forge/deploy"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/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/xrensiu/claude-code-forge/deploy"><img src="https://agentmods.dev/badge/commands/xrensiu/claude-code-forge/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.00516 |
| Opus 5.5 | $0.00000 | $0.00206 |
| Sonnet 5.5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
deploy 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy Command
Deploy code to target environment with pre-deploy verification.
Usage
/deploy [environment] [options]
Arguments
| Argument | Required | Default | Description |
|---|---|---|---|
| environment | Yes | - | Target: staging, production, preview |
Options
| Option | Description |
|---|---|
| --platform | Deployment platform (vercel/railway/cloudflare/custom) |
| --branch | Branch to deploy (default: current branch) |
| --skip-checks | Skip non-critical checks (hotfix mode) |
| --dry-run | Show what would be deployed without deploying |
| --rollback | Rollback to previous deployment |
Examples
# Deploy to staging
/deploy staging
# Deploy to production with specific platform
/deploy production --platform vercel
# Hotfix deployment (skip advisory checks)
/deploy production --skip-checks
# Preview what would be deployed
/deploy staging --dry-run
# Rollback last deployment
/deploy production --rollback
Workflow
-
Pre-deploy Checks
- Run test suite
- Verify build succeeds
- Security scan
- Environment variables check
-
Deployment
- Execute platform-specific deploy
- Wait for deployment completion
- Capture deployment URL/ID
-
Post-deploy Verification
- Health check
- Smoke test
- Monitor error rate
-
Report
- Deployment status
- URL/access info
- Rollback instructions
Agent Invocation
This command invokes the deployer agent:
agent: deployer
parameters:
ENVIRONMENT: [from argument]
PLATFORM: [from --platform or auto-detect]
BRANCH: [from --branch or current]
SKIP_CHECKS: [from --skip-checks]
Pre-requisites
- All tests passing
- Code review approved (for production)
- No uncommitted changes
- Platform CLI installed (vercel/railway/wrangler)
Exit Codes
| Code | Meaning |
|---|---|
| 0 | Deployment successful |
| 1 | Pre-deploy checks failed |
| 2 | Deployment failed |
| 3 | Post-deploy verification failed |
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 · 102 lines · 0 tokens per session scan A a4f88a0763ca
deploy is a command published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 516 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-09-05.
Other commands, from other repositories
otel-forward
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
platform
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
delivery
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
monitors
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
delivery-profiles
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
load-balancer
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.