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/restoregit 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.01141 |
| Opus 5 | $0.00000 | $0.00571 |
| Sonnet 5 | $0.00000 | $0.00228 |
| Haiku 4.5 | $0.00000 | $0.00114 |
Grade A, and why
restore 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:restore
Restore project state from a previously saved checkpoint with preview, diff comparison, and safety warnings.
| Level | L1 Vibe Coder |
| Category | State Management |
| Syntax | /forge:restore [checkpoint-name] [--preview] |
What It Does
/forge:restore is the dedicated restoration command -- a focused shortcut for /forge:checkpoint restore. When you provide a checkpoint ID, it reads the saved state, displays a side-by-side comparison of the checkpoint state versus your current state (branch, commit, uncommitted changes), and offers to restore the governance configuration. When no ID is provided, it lists all available checkpoints and lets you choose interactively.
The command prioritizes safety. It shows you exactly what will change before doing anything, warns if you have uncommitted changes that could be affected, and suggests creating a new checkpoint of your current state before restoring. Git state is displayed for reference but not automatically restored -- you get the exact git commands to run if you want to return to the checkpoint's code state, keeping destructive operations under your explicit control.
Without this command, restoring means remembering which checkpoint file to read, manually parsing the JSON, comparing it to your current state, and copying governance values by hand. /forge:restore handles all of that with safety checks at every step.
Syntax & Options
/forge:restore [checkpoint-name] [--preview]
| Option | Description |
|---|---|
checkpoint-name |
The ID of the checkpoint to restore. If omitted, shows an interactive list of all checkpoints. |
--preview |
Show what would be restored without making any changes. |
When to Use It
- After a failed experiment: Your refactoring broke something and you want to get back to a known-good state.
- After deployment issues: Roll back to the pre-deploy checkpoint created by
/forge:deploy. - Session recovery: Restore the checkpoint from the end of your last session to regain context.
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 · 124 lines · 0 tokens per session scan A dc487062536a
restore 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,141 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.
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…
paul:verify
Guide manual user acceptance testing of recently built features.
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.