Deploy

A deployment command that runs pre-release checks, builds and tests an application, sends it to a staging or production environment, checks its health, and notifies the team on Slack.

In plain words
What is it for?
Use it to release an application to staging or production and confirm that the deployed version is healthy.
Why use it?
It puts the expected release steps in one workflow, reducing the chance of skipping a check before or after deployment.

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/luongnv89/claude-howto/deploy
Clone the repo
git clone --depth 1 https://github.com/luongnv89/claude-howto
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 151 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.00008 $0.00151
Opus 5 $0.00004 $0.00076
Sonnet 5 $0.00002 $0.00030
Haiku 4.5 $0.00001 $0.00015

Measured yesterday against content hash 7b1d6ee69b3b, 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.

07-plugins/devops-automation/commands/deploy.md · 24 lines

What it actually says

Deploy Application

Execute deployment workflow:

  1. Run pre-deployment checks
  2. Build application
  3. Run tests
  4. Deploy to target environment
  5. Run health checks
  6. Notify team on Slack

Last Updated: August 4, 2026 Claude Code Version: 2.1.220 Sources:

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 · 24 lines · 8 tokens per session scan A 7b1d6ee69b3b

Subscribe to this mod's changes

Deploy is a command published in the GitHub repository luongnv89/claude-howto (41,271 stars, last pushed 6d ago), licensed MIT. It adds 8 tokens to every session and 151 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-30.