deploy

deploy is a command for coding agents from hainamchung/agent-assistant. It costs 9 tokens per session (457 once invoked), scanned A, original, MIT.

A deployment router that selects a readiness check, preview, production deployment, or rollback workflow based on the requested target.

In plain words
What is it for?
It helps check deployment readiness, deploy to staging or production, and roll back a deployment.
Why use it?
It removes the need to manually choose the correct deployment operation.

Command

Install

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.

agentmods
npx agentmods add commands/hainamchung/agent-assistant/deploy
Clone the repo
git clone --depth 1 https://github.com/hainamchung/agent-assistant

Wrote 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.

agentmods badge for deploy

README.md
[![agentmods](https://agentmods.dev/badge/commands/hainamchung/agent-assistant/deploy.svg)](https://agentmods.dev/commands/hainamchung/agent-assistant/deploy)
Your own site
<a href="https://agentmods.dev/commands/hainamchung/agent-assistant/deploy"><img src="https://agentmods.dev/badge/commands/hainamchung/agent-assistant/deploy.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 457 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00009 $0.00457
Opus 5 $0.00005 $0.00229
Sonnet 5 $0.00002 $0.00091
Haiku 4.5 $0.00001 $0.00046

Measured yesterday against content hash 1693d987adcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

commands/deploy.md · 72 lines

What it actually says

/deploy — Deployment Router

ROUTER DIRECTIVE: Analyze deployment target and route to appropriate workflow.

$ARGUMENTS


🛑 PRE-FLIGHT (DO FIRST — BLOCKS EXECUTION)

LOAD now (in order; path ./rules/ or ~/.{TOOL}/skills/agent-assistant/rules/):

  1. CORE.md — Identity, Laws, Routing
  2. PHASES.md — Phase Execution
  3. AGENTS.md — Tiered Execution

⛔ Do not run any workflow phase until all are loaded. Follow all rules in those files. Then run this file's ROUTING LOGIC, LOAD the chosen variant workflow, and execute it.


ROUTING LOGIC

IF target is "check" or "status":
  → Route to /deploy:check

IF target is "preview" or "staging":
  → Route to /deploy:preview

IF target is "production" or "prod":
  → Route to /deploy:production

IF target is "rollback":
  → Route to /deploy:rollback

AVAILABLE ROUTES

Route When to Use
/deploy:check Pre-deployment readiness check
/deploy:preview Deploy to preview/staging
/deploy:production Deploy to production
/deploy:rollback Rollback deployment

PRESENT OPTIONS

## 🚀 Deployment Mode Selection

**Target**: [parsed target]

**Choose workflow:**

1. ✅ **Check** → `/deploy:check` — Readiness verification
2. 🔍 **Preview** → `/deploy:preview` — Staging deployment
3. 🚀 **Production** → `/deploy:production` — Production release
4. ⏪ **Rollback** → `/deploy:rollback` — Revert deployment

⏳ Awaiting selection...
Changes

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.

  1. yesterday First seen · 72 lines · 9 tokens per session scan A 1693d987adcf

Subscribe to this mod's changes

deploy is a command published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 457 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-09-03.