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/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/deploy)<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.
<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>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.00008 | $0.00853 |
| Opus 5.5 | $0.00003 | $0.00341 |
| Sonnet 5.5 | $0.00002 | $0.00171 |
| Haiku 4.5 | $0.00001 | $0.00085 |
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.
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
- Create pre-deploy checkpoint:
mkdir -p .claude/checkpoints
Save checkpoint with ID pre-deploy-{timestamp}.
- Build:
npm run build 2>&1
- Deploy (project-specific):
# Check for deploy script in package.json
npm run deploy 2>/dev/null || echo "No deploy script found"
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.
- 12d ago Changed 01c3265cdacf
- 1mo ago Changed · +17 lines · +8 tokens per session d4bdefdd9cb4
- 1mo ago First seen · 136 lines · 0 tokens per session scan A 313535e9fda3
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.
Other commands, from other repositories
update-changelog
Update CHANGELOG.md with new entry based on git diff.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
hatch3r-release
Release-workflow orchestrator — preflight, SemVer bump, changelog sync, build + CycloneDX SBOM, adapter-output verification, quality gates, release-notes reconciliation, then stop before publish/merge for human approval.
pre-release
Parallel pre-release check — fires release-captain + security-reviewer + code-reviewer simultaneously. Go/no-go in one command before you ship.
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
release
You are executing the release workflow for a project with a dev → main branch protocol.