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/updategit 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.01073 |
| Opus 5 | $0.00000 | $0.00536 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
update 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:update
Update the Forge plugin to the latest version with a built-in workaround for Claude Code's stale marketplace cache (bug #29071).
| Level | L1 Vibe Coder |
| Category | Setup & Maintenance |
| Syntax | /forge:update [--check] [--plugin] [--config] |
What It Does
/forge:update handles the full plugin update lifecycle, including a workaround for a known Claude Code issue (#29071) where plugin update fetches new content but never merges it into the local marketplace clone. The command first detects your current installation (plugin name, scope, marketplace version), then manually pulls the latest from the marketplace git clone, and finally runs the standard update command. If the standard update fails, it escalates through progressively more aggressive methods: scope-specific updates, full reinstall, and finally a nuclear clean install.
After the plugin update, the command also checks your project configuration: verifying governance.json is valid, checking if the schema needs migration, and confirming hooks are configured. This ensures that both the plugin and your project config are current.
The critical detail: after any update, commands, agents, and skills only reload on session restart. The command tells you this clearly and suggests restarting Claude Code to pick up changes.
Syntax & Options
/forge:update [--check] [--plugin] [--config]
| Option | Description |
|---|---|
--check |
Only check what version is available without making changes |
--plugin |
Only update the plugin itself, skip project config check |
--config |
Only check and update project governance config and hooks |
When to Use It
- After a new Forge release: Update to get the latest commands, agents, and skills.
- When commands seem outdated: If a command is missing features documented online, you may be on a stale version.
- Troubleshooting plugin issues: The escalation chain (standard update -> reinstall -> clean install) resolves most plugin problems.
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.
- 2d ago First seen · 122 lines · 0 tokens per session scan A b591ff956757
update 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,073 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.