forge: Instructions file for Claude Code

CLAUDE.md

forge CLAUDE.md is an instructions file for Claude Code from firatcand/forge. It costs 463 tokens per session, scanned A, original, MIT.

Project instructions for Forge that combine its development methods with the repository's project specification and coding commands.

In plain words
What is it for?
Use them when starting work in Forge, running its build, tests, type checks, or development server, and changing framework code that becomes part of its public release.
Why use it?
They help new contributors load the right project context and distinguish the framework's working method from the repository's intended product behaviour.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code.

This is firatcand/forge's own configuration. It tells Claude Code how to work on forge itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything forge configures →

Reuse

Borrowing it

Nothing to install: this file belongs to firatcand/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/firatcand/forge/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/firatcand/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.

agentmods badge for forge CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/firatcand/forge/claude-md/github.svg)](https://agentmods.dev/instructions/firatcand/forge/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/firatcand/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/firatcand/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.

agentmods 80×15 button for forge CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/firatcand/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/firatcand/forge/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 463 This file is loaded in full into every session.
When invoked 463 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00463 $0.00463
Opus 5.5 $0.00185 $0.00185
Sonnet 5.5 $0.00093 $0.00093
Haiku 4.5 $0.00046 $0.00046

Measured 1mo ago against content hash e7ee7aa08f15, 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 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.

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 · 50 lines

What it actually says

This project uses Forge. The methodology below is imported from a local file regenerated by forge upgrade. New collaborator? Install Forge with:

npm install -g @firatcand/forge
forge upgrade

First time opening this repo in Claude Code? You'll see a one-time prompt asking permission to load .forge/CONTEXT.md. Accept it — without that approval, Claude Code silently skips the import and the methodology context won't be available.

@.forge/CONTEXT.md

The import below pulls in THIS project's spec — the synthesized BRIEF/PRD/SPEC (the "what", vs. the methodology "how" above). It is committed and generated by /ingest-spec (a stub until you run it), so it travels with the repo.

@spec/CONTEXT.md

forge

Note: This is the forge repo itself. Iterating on this repo means iterating on the framework — every change ships to npm publish @firatcand/forge and lands on adopter machines via npx @firatcand/forge. Treat all changes as public-API.

Stack

Commands

  • Build: npm run build
  • Test: npm test
  • Type check: npm run typecheck
  • Lint: npm run lint (ESLint — unused vars/imports + unreachable; non-blocking, warnings only)
  • Dev: npm run dev
  • Render methodology context (one-shot, until Phase B's forge upgrade ships): npm run forge:render-context

Conventions

  • Functional components only, no class components
  • Always handle errors explicitly — no silent catches
  • New API routes must have input validation
  • See spec/ for full conventions

Critical paths

See CRITICAL.md

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.

  1. 1mo ago First seen · 50 lines · 463 tokens per session scan A e7ee7aa08f15

Subscribe to this mod's changes

forge CLAUDE.md is an instructions file published in the GitHub repository firatcand/forge (13 stars, last pushed 3mo ago), licensed MIT. It adds 463 tokens to every session, about $0.0019 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.

Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens