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/forgeyclap/claude-forge/setup-forgegit clone --depth 1 https://github.com/ForgeyClap/claude-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/forgeyclap/claude-forge/setup-forge)<a href="https://agentmods.dev/commands/forgeyclap/claude-forge/setup-forge"><img src="https://agentmods.dev/badge/commands/forgeyclap/claude-forge/setup-forge.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.00053 | $0.02890 |
| Opus 5 | $0.00026 | $0.01445 |
| Sonnet 5 | $0.00011 | $0.00578 |
| Haiku 4.5 | $0.00005 | $0.00289 |
Grade B, and why
setup-forge scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
values into the gitignored `.env`, best-effort `chmod 600`, and writes a values-free How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-forge — Forge first-run onboarding wizard (global core)
Run the Forge onboarding for: $ARGUMENTS
This is the bare /setup-forge installed into ~/.claude by the Forge installer. It runs in
the current project folder. You (the Lead agent) drive a friendly, beginner-safe onboarding;
the mechanical and security-sensitive steps are done by a zero-dependency engine you call —
node .claude/forge-bin/forge-setup.cjs (resolved in the current project) — never by hand.
Non-negotiable honesty & safety rules
- Never print or echo a secret value — names only, never "to confirm".
- Never claim a step ran if it didn't. Report exactly what the engine returned.
- Never write a secret to a git-tracked file. The engine enforces this; don't shortcut it.
- Never delete or overwrite the user's own files without saying so first.
- Keys are optional — a newcomer can skip and still finish. Forge runs without keys.
- Work only in this project folder. Don't touch other projects. The only global writes are the documented markers.
Global route — locate the engine first
Because this command lives in ~/.claude, the project may or may not have the full Forge payload
yet. Check before anything else:
- If
.claude/forge-bin/forge-setup.cjsexists in the current project → use it (normal flow below). - If it is missing, the per-project payload isn't installed here. Say so plainly and offer the
fix: run the installer (
install.shon macOS/Linux,install.ps1on Windows) from theclaude-forgerepo, or copy.claude/into this project manually. Once present, re-run/setup-forge. Do not fabricate a key flow or dashboard that isn't installed.
Language first (internationalization)
Determine the working language so the entire wizard and every confirmation run in it:
node .claude/forge-bin/forge-setup.cjs lang(printsendefault) — if the engine is absent, fall back to English and to any--langflag.- A
--lang <code>flag in $ARGUMENTS overrides. - On a fresh run, ask it as question 4 below.
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 · 174 lines · 0 tokens per session scan B 767e241e99a4
setup-forge is a command published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 2,890 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.