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/lucasduys/forge/resumegit clone --depth 1 https://github.com/LucasDuys/forgeWrote 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/lucasduys/forge/resume)<a href="https://agentmods.dev/commands/lucasduys/forge/resume"><img src="https://agentmods.dev/badge/commands/lucasduys/forge/resume.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.01591 |
| Opus 5 | $0.00004 | $0.00796 |
| Sonnet 5 | $0.00002 | $0.00318 |
| Haiku 4.5 | $0.00001 | $0.00159 |
Grade A, and why
resume 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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Resume
Continue an in-progress Forge execution from where it left off after a context reset, session close, or manual pause.
Step 1: Verify Forge project exists
Check if .forge/ exists. If it does not, stop and tell the user:
No Forge project found. Run
/forge brainstormto get started.
Step 1.5: Forensic recovery (T020, R007/R008)
Before loading any state, run forensic recovery. This handles crashed sessions, stale locks, budget exhaustion, and orphan worktrees. The forensic recovery scan is always safe to run -- on a clean state it is a no-op.
node "${CLAUDE_PLUGIN_ROOT}/scripts/forge-tools.cjs" forensic-recover --forge-dir .forge
The command:
- Sets phase to
recoveringwhile it runs - Inspects
.forge/.forge-loop.lock-- takes over stale locks (heartbeat older than 5 minutes) - Reads checkpoints from
.forge/progress/to find in-flight tasks - Cross-references git log +
task-status.jsonto identify committed tasks - Lists worktrees and flags any orphans (worktrees for tasks not in any frontier or already committed)
- If
phase: budget_exhausted, reads.forge/resume.mdand surfaces the reason - Writes a caveman-form summary to
.forge/state.mdnotes - Sets final phase to
idle(clean) orneeds_human(warnings present) - Exits 0 on clean recovery, exit 2 if
needs_human
Show the recovery report to the user. Read it carefully:
- If the report lists orphan worktrees, do NOT delete them automatically. Tell the user which paths are orphan and that they need to run
git worktree remove <path>manually after reviewing the contents. - If the report says
Needs human: YES, stop and ask the user how to proceed. Common cases: budget exhausted (raise the cap in.forge/config.json), live lock from another session (verify no other forge instance is running). - If
Resume pointis present, that is the task you will continue from in Step 6. - In full autonomy mode, auto-continue if
Needs human: noand there are no warnings. Otherwise pause and prompt.
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.
- 4d ago First seen · 123 lines · 8 tokens per session scan A c1590d1536cb
resume is a command published in the GitHub repository LucasDuys/forge (55 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 1,591 once invoked, about $0.0000 per session on Opus 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-30.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.
setup
Diagnose-first project setup with state machine — scans, confirms, interviews, writes.
scan
Scan AWS account for cost optimization.