deploy

deploy is a command for Claude Code from nxtg-ai/forge-plugin. It costs 8 tokens per session (853 once invoked), scanned A, original, MIT.

A deployment command that checks a project before releasing it. It validates TypeScript compilation, tests, security, git status, and the production build, then can run the project's deployment script after confirmation.

In plain words
What is it for?
Use it to validate a release, perform a dry run, deploy after the checks pass, or create a rollback checkpoint and review the deployed version details.
Why use it?
It catches common release problems before deployment and blocks the release when a required check fails, with guidance on what needs fixing.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the nxtg-forge plugin — 27 skills, 24 commands, 33 agents shipped together

Good fit Use it to validate a release, perform a dry run, deploy after the checks pass, or create a rollback checkpoint and review the deployed version details.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/nxtg-ai/forge-plugin/deploy
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.

Clone the repo
git clone --depth 1 https://github.com/nxtg-ai/forge-plugin

Made for: Claude Code.

Or install nxtg-forge, the plugin that ships this one along with the rest of its 27 skills, 24 commands, 33 agents.

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/nxtg-ai/forge-plugin/deploy/github.svg)](https://agentmods.dev/commands/nxtg-ai/forge-plugin/deploy)
Your own site
<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/deploy"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/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.

agentmods 80×15 button for deploy

Your own site · 80×15
<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/deploy"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/deploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 853 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00008 $0.00853
Opus 5.5 $0.00003 $0.00341
Sonnet 5.5 $0.00002 $0.00171
Haiku 4.5 $0.00001 $0.00085

Measured 12d ago against content hash 01c3265cdacf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 12d 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.

plugins/nxtg-forge/commands/deploy.md · 153 lines

How it starts

The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.

NXTG-Forge Deploy

You are the Deployment Manager - validate and deploy the application with comprehensive safety checks.

Parse Arguments

Arguments received: $ARGUMENTS

Options:

  • No arguments: Interactive deployment with full validation
  • --validate-only: Run pre-deployment checks only, don't deploy
  • --dry-run: Show what would happen without executing
  • --skip-tests: Skip test execution (not recommended)

Step 1: Pre-Deployment Validation

Run all checks and report status:

1a. TypeScript Check

npx tsc --noEmit 2>&1

1b. Test Suite

npx vitest run --reporter=verbose 2>&1

1c. Security Audit

npm audit 2>/dev/null

1d. Git Status

git status --porcelain
git log --oneline -1

1e. Build Check

npm run build 2>&1

Display validation results:

PRE-DEPLOYMENT VALIDATION
===========================

  TypeScript:  {PASS / FAIL - N errors}
  Tests:       {PASS / FAIL - N/M passing}
  Security:    {PASS / WARN - N vulnerabilities}
  Git:         {CLEAN / DIRTY - N uncommitted}
  Build:       {PASS / FAIL}

  Overall: {READY / NOT READY}

If --validate-only, stop here.

Step 2: Deployment Decision

If any checks failed:

Deployment blocked:
  - {list of failed checks}

Fix these issues before deploying:
  /nxtg-forge:test    Fix failing tests
  /nxtg-forge:optimize  Address code issues

If all checks pass, ask user to confirm:

All checks passing. Ready to deploy.

Deploy now? This will:
  1. Build the project
  2. Run the deploy script (if configured)
  3. Create a deployment checkpoint

Proceed?

Use AskUserQuestion for confirmation.

Step 3: Deploy

  1. Create pre-deploy checkpoint:
mkdir -p .claude/checkpoints

Save checkpoint with ID pre-deploy-{timestamp}.

  1. Build:
npm run build 2>&1
  1. Deploy (project-specific):
# Check for deploy script in package.json
npm run deploy 2>/dev/null || echo "No deploy script found"

Read the full file on GitHub · 153 lines

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. 12d ago Changed 01c3265cdacf
  2. 1mo ago Changed · +17 lines · +8 tokens per session d4bdefdd9cb4
  3. 1mo ago First seen · 136 lines · 0 tokens per session scan A 313535e9fda3

Subscribe to this mod's changes

deploy is a command published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 853 once invoked, about $0.0000 per session on Opus 5.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.