Borrowing it
Nothing to install: this file belongs to ForgeAILab/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/ForgeAILab/forge/main/CLAUDE.mdgit clone --depth 1 https://github.com/ForgeAILab/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/forgeailab/forge/claude-md)<a href="https://agentmods.dev/instructions/forgeailab/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/forgeailab/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.
<a href="https://agentmods.dev/instructions/forgeailab/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/forgeailab/forge/claude-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.03104 | $0.03104 |
| Opus 5.5 | $0.01242 | $0.01242 |
| Sonnet 5.5 | $0.00621 | $0.00621 |
| Haiku 4.5 | $0.00310 | $0.00310 |
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 5d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
The user-facing entry point is README.md. Deeper material is split across docs/:
- docs/architecture.md — crate graph, state machine, workflow engine, DB.
- docs/api.md — REST surface, pagination, MCP tools.
- docs/getting-started.md — install, configuration, end-to-end walkthrough.
- docs/cli.md —
forge-ctlreference.
When you change behavior, update the relevant docs/ file in the same change. Treat README as a launch landing page — keep it short and link out.
Project status: Public Beta (pre-1.0)
Forge is in public beta. The local-first single-user product is shipping to real users, but we are still pre-1.0 and pre-stable.
What that means for changes you make:
- Breaking changes are allowed, but they must be visible: update CHANGELOG.md under the
Unreleasedsection with a### Breakingentry, and bump the workspace version when cutting a release. Silent breakage is no longer acceptable now that users exist. - No backward-compat shims, no
_v2suffixes, no deprecated aliases. When something changes, update all call sites and delete the old code. Express the break in the changelog, not in the source. - No feature flags for rollout safety. Ship the new behavior directly.
- Database migrations must preserve user data unless the user explicitly opts in to a destructive migration (e.g. a hard schema reset for the dev
./testdata dir). Add a new numbered migration; do not edit historical ones. - Public surfaces — REST endpoints, MCP tool names,
forge-ctlflag names, event payload shapes, JSONL log schema, on-disk file layout — are the ones to be most deliberate about. Internal Rust APIs and crate boundaries can still move freely. - When a spec/design changes, rewrite the affected code to match. Don't layer the new design on top of the old one.
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.
- 5d ago Changed · +2 lines · +166 tokens per session da7ea2ecf7d3
- 8d ago Changed · +2 lines · +109 tokens per session a25fea56c2e2
- 12d ago Changed · +22 lines · +497 tokens per session 34ba7e5abd22
- 28d ago Changed · +112 tokens per session e3bd907cee69
- 1mo ago Changed · +2 lines · +90 tokens per session 5fe0cebe940a
- 1mo ago Changed · +8 tokens per session e1b2bdbf281e
- 2mo ago First seen · 123 lines · 2,122 tokens per session scan A 2733912aee2d
forge CLAUDE.md is an instructions file published in the GitHub repository ForgeAILab/forge (28 stars, last pushed 2d ago), licensed MIT. It adds 3,104 tokens to every session, about $0.0124 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.
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.