Borrowing it
Nothing to install: this file belongs to ForgeyClap/claude-forge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ForgeyClap/claude-forge/main/AGENTS.mdgit 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/instructions/forgeyclap/claude-forge/agents-md)<a href="https://agentmods.dev/instructions/forgeyclap/claude-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/forgeyclap/claude-forge/agents-md/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/instructions/forgeyclap/claude-forge/agents-md"><img src="https://agentmods.dev/badge/instructions/forgeyclap/claude-forge/agents-md.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.03587 | $0.03587 |
| Opus 5.5 | $0.01435 | $0.01435 |
| Sonnet 5.5 | $0.00717 | $0.00717 |
| Haiku 4.5 | $0.00359 | $0.00359 |
Grade A, and why
claude-forge AGENTS.md 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 28d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents
Forge ships 19 built-in agents — 12 permanent Bosses plus 7 on-demand specialists — and turns Claude Code into a coordinated team that builds, tests, reviews and ships. Every one is a real Claude Code Agent-tool subagent defined in .claude/agents/*.md, not a simulated persona or a fabricated name on a dashboard.
[!NOTE] Honest count. The full install ships 19 agents (12 permanent Bosses + 7 specialists) and 72 skills (51 Forge skills + 21 vendored public skills); the LITE plugin carries 18 agents and 22 skills. Counts are taken from the directories, not typed by hand. Forge can also route to your wider agent ecosystem (ECC / Claude-Code agent types) when a task calls for something outside the built-ins — but those are not part of this repo. When you see large numbers elsewhere, that is the routable ecosystem, not what claude-forge ships. See Routing to your wider ecosystem.
How Forge uses agents
Forge is a hierarchy, not a free-for-all. Work flows top-down and quality flows bottom-up:
You (orchestrator) ── /forge <task>
│
▼
Boss (Lead) ──► Head Chef ──► domain Bosses + specialists
owns mission splits into do the actual work
work packages
▲ │
└──────── QA fix-loop ◄───── Test Boss / Review Boss
- Lead → Bosses → specialists. The Boss owns the mission; Head Chef breaks it into exact work packages; the right domain Bosses and specialists execute; Test Boss and Review Boss gate the result.
- Real subagents. Each agent is dispatched via the Claude Code Agent tool with its own model, tools and effort budget (from its frontmatter). Nothing is theatre.
- Dynamic, right-sized teams. Forge picks the smallest relevant team per task (see the fan-out levels in
CLAUDE.md): a one-line fix gets one or two agents; a full-stack build gets a phased swarm. Forge does not over-spawn to look impressive, and does not lock to a fixed count. - Honest ledger. Every run records which agents actually worked in
FORGE_AGENT_LEDGER.md, with evidence and one of the fixed statuses —REAL INVOKED·REAL TOOL/SKILL USED·INTERNAL ROLE ONLY·NOT USED·FAILED. No fake "done", no invented tests, no imaginary agents.
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.
- 28d ago Changed 52ab0f4c8487
- 1mo ago Changed · -2 tokens per session 9046241aa431
- 1mo ago Changed · +21 lines · +678 tokens per session 40fece3aa79e
- 1mo ago Changed · +1 lines · +157 tokens per session db18be591535
- 1mo ago First seen · 120 lines · 2,754 tokens per session scan A ad32fce26a11
claude-forge AGENTS.md is an instructions file published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 29d ago), licensed MIT. It adds 3,587 tokens to every session, about $0.0143 per session on Opus 5.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-09-03.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.