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/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/forgeyclap/claude-forge/claude-md"><img src="https://agentmods.dev/badge/instructions/forgeyclap/claude-forge/claude-md.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.1 | $0.02021 | $0.02021 |
| Opus 5 | $0.01010 | $0.01010 |
| Sonnet 5 | $0.00404 | $0.00404 |
| Haiku 4.5 | $0.00202 | $0.00202 |
Grade A, and why
claude-forge CLAUDE.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 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Forge V2 (project-local, security-light)
This project runs Forge V2: a universal, dynamic multi-agent build / automation / review / delivery system on top of ECC. It handles new and existing work across websites, landing pages, full-stack apps, n8n builds, AI chatbots / RAG, Telegram bots, prediction & data systems, scraping, business automations, API integrations, dashboards, refactors, audits, research, and debugging.
Standing rules, not a procedure — the procedure lives in /forge and the skills.
Forge Studio v7 (how Forge works)
This is the clearly-marked Forge section. When Forge safe-merges into an existing
CLAUDE.md, only this## Forge Studio v7section is added/updated — existing project rules are preserved.
Lead Agent (you) → Mission Blueprint + Skill Discovery → dynamic role-based subagents (ECC-first, incl. custom roles) → outputs → Lead Review → bounded rework/fix loop → merge → optional Codex → quality gate → honest forge-report.
Plan before executing. Pick the smallest relevant team via forge-router; the role/skill examples are guidance, not limits — create custom subagent roles + safe project-local custom skills for gaps, and a custom taxonomy for unknown project types. Small task = small team; large/high-end = larger swarm. Don't over-spawn; don't lock to a fixed number.
- ECC-first (ECC Normal Mode — default ON): prefer real ECC agents/skills; native only as a labeled fallback. ECC Full Test Mode is opt-in only (default OFF) via
.claude/FORGE_ECC_MODE.json. - Forge Session Mode:
/forge/gebruik Forgestart a project-local session (.claude/FORGE_SESSION_STATE.json) so follow-ups auto-use Forge untilstop Forge/pause Forge. No extra permission granted. - Project agent strategy: see
FORGE_PROJECT_PROFILE.mdfor the project type, recommended + custom subagent roles, role mapping, and rework-loop rules. - Project skill strategy: Skill Discovery selects skill packs + creates project-local custom skills (
.claude/skills/<name>/SKILL.md); fallback = labeled native or BLOCKED. Every executable subagent gets an assigned skill/method. - Quality gates: advisory review only unless you ask for blocking gates; Codex optional (logged real/blocked/not-invoked); QA/retest in the rework loop.
- Forge maintains four things: this
CLAUDE.md(project brain) ·.claude/skills/*/SKILL.md(capabilities) · Forge memory · the dashboard.
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 · 69 lines · 2,021 tokens per session scan A b9e3b7bac674
claude-forge CLAUDE.md is an instructions file published in the GitHub repository ForgeyClap/claude-forge (2 stars, last pushed 1mo ago), licensed MIT. It adds 2,021 tokens to every session, about $0.0101 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-09-03.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.