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.
npx agentmods add commands/nxtg-ai/forge-plugin/deploygit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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 | $0.00000 | $0.01202 |
| Opus 5 | $0.00000 | $0.00601 |
| Sonnet 5 | $0.00000 | $0.00240 |
| Haiku 4.5 | $0.00000 | $0.00120 |
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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:deploy
Deploy with comprehensive pre-flight validation -- type checking, tests, security audit, build verification, and git cleanliness -- before executing the deployment.
| Level | L1 Vibe Coder |
| Category | Quality & Testing |
| Syntax | /forge:deploy [--validate-only] [--dry-run] [--skip-tests] |
What It Does
/forge:deploy is the safety-first deployment command. Before any deployment action occurs, it runs a five-point pre-flight validation: TypeScript compilation, full test suite, security audit, git cleanliness check, and production build. Each check produces a PASS or FAIL result, and the overall verdict is READY or NOT READY. If any check fails, deployment is blocked with specific guidance on what to fix.
When all checks pass and you confirm, the command creates a pre-deployment checkpoint (so you can roll back), executes the build, and runs your project's deploy script. If no deploy script exists in package.json, it suggests common deployment targets: Vercel, Netlify, Docker, or custom SCP. After deployment, it shows the version, commit hash, branch, and checkpoint ID for rollback.
Without this command, deployment is a manual checklist: run tests, check types, audit dependencies, verify git is clean, build, deploy, hope nothing was missed. /forge:deploy enforces the checklist programmatically and creates an automatic rollback point.
Syntax & Options
/forge:deploy [--validate-only] [--dry-run] [--skip-tests]
| Option | Description |
|---|---|
--validate-only |
Run all pre-deployment checks without deploying. Useful as a CI gate. |
--dry-run |
Show what would happen at each step without executing any actions |
--skip-tests |
Skip the test suite execution (not recommended; the command warns you) |
When to Use It
- Before any production deployment: Run the full pipeline to catch issues before they reach users.
- As a CI validation gate: Use
--validate-onlyto run all checks without deploying, suitable for pull request checks. - After a sprint of changes: When you have accumulated multiple commits and want to deploy with confidence.
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.
- yesterday First seen · 136 lines · 0 tokens per session scan A 313535e9fda3
deploy is a command published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,202 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-08-31.
Other commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
paul:verify
Guide manual user acceptance testing of recently built features.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.