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/executegit clone --depth 1 https://github.com/LucasDuys/forgeWhat 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.00005 | $0.03313 |
| Opus 5 | $0.00003 | $0.01656 |
| Sonnet 5 | $0.00001 | $0.00663 |
| Haiku 4.5 | $0.00001 | $0.00331 |
Grade A, and why
execute 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Execute
First-Run Wizard (R004.AC3)
Before anything else, fire the one-shot token-reduction wizard. Idempotent — prints once on first install, then no-ops forever. Suppressed when /forge:watch is rendering its own banner (R004.AC6).
node "${CLAUDE_PLUGIN_ROOT}/scripts/forge-wizard.cjs" --forge-dir .forge
Launch the autonomous implementation loop. Reads the frontier, implements tasks one by one, and relies on the Stop hook state machine to drive iteration until all tasks are complete.
Live status header. Every iteration of /forge:execute is automatically prefixed with a compact dashboard-style status block (phase, current task + step, agent, progress bar, tokens, per-task budget, lock status). You see what forge is doing without leaving Claude Code or running a separate command. The block is generated by scripts/forge-status-block.cjs, called from the Stop hook on every iteration. Opt out by setting execute.status_header: false in .forge/config.json. For a fullscreen ANSI dashboard in a separate terminal window, use /forge:watch instead.
New in v2.1
- Token budgets are now enforced as hard ceilings, not warnings. Exhaustion transitions to
budget_exhaustedphase with a handoff doc at.forge/resume.md. - Git worktree isolation per task: each task runs in
.forge/worktrees/{task-id}/and is squash-merged on success. - Lock file acquisition at session start: refuses to run if another valid lock is held (unless stale >5min).
- Per-task checkpoints at each step: resume picks up exactly where the last checkpoint was written.
- Headless mode for CI: see
node scripts/forge-tools.cjs headless execute --helpfor non-interactive usage with exit codes.
Pre-flight Check
The Forge workflow is strictly sequential: brainstorm -> plan -> execute. These pre-flight checks enforce that the prior phases completed correctly. If any check fails, stop and tell the user what to run first.
- Verify
.forge/exists. If it does not, stop and tell the user:.forge/not found. Run/forge brainstormfirst to generate specifications, then/forge planto create task frontiers.
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 · 225 lines · 5 tokens per session scan A 9d8f16ee2f34
execute is a command published in the GitHub repository LucasDuys/forge (55 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 3,313 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
discover
Run a full user research cycle — persona creation, empathy mapping, and journey mapping for a product or feature.
test-plan
Run the full usability study workflow — research questions, participant criteria, tasks, metrics, and facilitation guide.
eg-new-feature
Build a new feature using the elephant/goldfish workflow — design doc, goldfish design check, implement, review, validate.
eg-precommit-review
Run the pre-commit independent-reviewer loop on the current branch's pending changes.
eg-fix-bug
Fix a bug using the elephant/goldfish workflow — problem doc, goldfish diagnosis check, failing test, fix, review, validate.
verify-custom-rules
Verify custom rules for Safety Net.