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.
git 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.03087 |
| Opus 5.5 | $0.00000 | $0.01235 |
| Sonnet 5.5 | $0.00000 | $0.00617 |
| Haiku 4.5 | $0.00000 | $0.00309 |
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 1mo 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.
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 — 177 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, install the per-project payload yourself right now — run the
forge-coreskill's INSTALLER phases (it copies from~/.claude/forge/template/, which the global install already put there), then continue with the flow below. Only if that template is also missing (a very old or partial global install) say so plainly and continue with a light onboarding (Step 2 only, no key flow, no dashboard) — never ask the user to run an installer command themselves, and 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.
- 1mo ago Changed · +3 lines 317ee8a22070
- 2mo ago 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 costs nothing until one of its globs matches a file; then it loads 3,087 tokens. 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.
setup-forge compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| setup-forgeForgeyClap/claude-forge | Command | 2 | 1mo ago | MIT | B | 0 | Claude Code |
| scout-meta-reviewRaven-Scout/Scout | Command | 20 | yesterday | MIT | A | 61 | Claude Code |
| scout-workRaven-Scout/Scout | Command | 20 | yesterday | MIT | A | 47 | Claude Code |
| dashboardToRvaLDz/trailhead | Command | 27 | 2d ago | MIT | A | 20 | Claude Code |
| pauseToRvaLDz/trailhead | Command | 27 | 2d ago | MIT | A | 11 | Claude Code |
| auditToRvaLDz/trailhead | Command | 27 | 2d ago | MIT | A | 28 | Claude Code |
| splitToRvaLDz/trailhead | Command | 27 | 2d ago | MIT | A | 10 | Claude Code |