What is forge CLAUDE.md?

Project instructions for Forge, a Claude Code plugin that guides software work from an idea through planning and implementation. It describes Forge's commands, folders, and required workflow.

It helps with brainstorming, writing specifications and plans, executing code changes, and using Forge's specialist agents, hooks, and templates.

It gives the coding agent the project rules and structure needed to follow the intended development process.

How LucasDuys/forge configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to LucasDuys/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.

Copy the file

curl -O https://raw.githubusercontent.com/LucasDuys/forge/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/LucasDuys/forge

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/lucasduys/forge/claude-md/github.svg)](https://agentmods.dev/instructions/lucasduys/forge/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/lucasduys/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/lucasduys/forge/claude-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/lucasduys/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/lucasduys/forge/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,828 This file is loaded in full into every session.

When invoked 2,828 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02828	$0.02828
Opus 5.5	$0.01131	$0.01131
Sonnet 5.5	$0.00566	$0.00566
Haiku 4.5	$0.00283	$0.00283

Measured 2mo ago against content hash bce64c516cd9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

CLAUDE.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Forge — Autonomous Agent Coding System

What This Is

Forge is a Claude Code CLI plugin that provides an autonomous, spec-driven development loop. Three commands: /forge brainstorm, /forge plan, /forge execute — they chain together to take an idea from concept to working code with minimal human intervention.

Project Structure

forge/
├── .claude-plugin/plugin.json     — Plugin manifest
├── commands/                      — Slash commands (/forge brainstorm, plan, execute, etc.)
├── skills/                        — Procedural workflows + cross-cutting skills (guardrails, graphify, design-system)
├── agents/                        — Specialized subagents (speccer, planner, executor, reviewer, verifier, researcher)
├── hooks/                         — Stop hook (loop engine), token monitor (PostToolUse)
├── scripts/                       — JS utility (forge-tools.cjs) + bash helpers
├── templates/                     — Output file templates (spec, plan, state, summary)
├── references/                    — Reference docs (token profiles, backprop patterns, multi-repo, etc.)
└── docs/superpowers/specs/        — Design specs for this project

Workflow Enforcement (CRITICAL)

The Forge workflow is strictly sequential: brainstorm -> plan -> execute. This is enforced at multiple levels:

Spec approval gate: Only the brainstorming skill writes status: approved specs, and only after explicit user approval of an approach. The execute command validates this.
Frontier requirement: /forge execute validates that every approved spec has a corresponding frontier file from /forge plan.
Programmatic validation: forge-tools.cjs setup-state runs validateWorkflowPrerequisites() which checks spec approval status and frontier existence before allowing execution.
State machine phases: brainstorming and planning are formal phases in the state machine (see references/state-machine.md).

Never skip brainstorming. Even if the user's request seems clear, the interactive Q&A surfaces hidden assumptions, the approach proposals prevent over-engineering, and the approved spec provides verifiable acceptance criteria for the reviewer and verifier.

Read the full file on GitHub · 207 lines

Changes

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.

2mo ago First seen · 207 lines · 2,828 tokens per session scan A bce64c516cd9

Subscribe to this mod's changes

forge CLAUDE.md is an instructions file published in the GitHub repository LucasDuys/forge (57 stars, last pushed 3mo ago), licensed MIT. It adds 2,828 tokens to every session, about $0.0113 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-08-30.

Building agents Planning agentic-ai ai-agent ai-coding-agent ai-tools anthropic automation

forge CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
forge CLAUDE.mdLucasDuys/forge	Instructions file	57	3mo ago	MIT	A	2,828	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

forge: Instructions file for Claude Code