forge: Instructions file for Claude Code

CLAUDE.md

forge CLAUDE.md is an instructions file for Claude Code from SidCorp-co/forge. It costs 2,484 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for Forge, an open-source control system for managing projects and running an AI-agent pipeline. They describe its backend, web interface, shared types, Rust runner, database, WebSocket connection, and MCP server.

In plain words
What is it for?
Navigating the Forge workspace, choosing the correct package for a change, understanding data and agent-pipeline connections, and following the project's documented commands and rules.
Why use it?
They tell coding agents where the main parts of the system live and which project principles guide changes. This reduces guesswork when working across the backend, web app, runner, and shared contracts.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is SidCorp-co/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 SidCorp-co/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/SidCorp-co/forge/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/SidCorp-co/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/sidcorp-co/forge/claude-md/github.svg)](https://agentmods.dev/instructions/sidcorp-co/forge/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/sidcorp-co/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/sidcorp-co/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/sidcorp-co/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/sidcorp-co/forge/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,484 This file is loaded in full into every session.
When invoked 2,484 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.02484 $0.02484
Opus 5.5 $0.00994 $0.00994
Sonnet 5.5 $0.00497 $0.00497
Haiku 4.5 $0.00248 $0.00248

Measured 29d ago against content hash d3b34e3b4ca1, 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 29d 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 · 173 lines

How it starts

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

@.forge/orientation.md

Forge

Constitution: docs/VISION.md — what Forge is / is not, why, who, and the principles (incl. VISION: state-never-lies, VISION: kernel-hard-policy-soft). Intent only: no architecture, no versions, no roadmap. On intent conflicts, VISION wins — cite it by name, never by section number.

Workspace

Package What
packages/core Hono backend over Drizzle/Postgres, mounting per-domain routes from packages/core/src/index.ts; also the WebSocket server, the MCP server, and the job pool a master agent claims from.
packages/web-v2 Next.js cloud UI, canonical at /. Feature modules under src/features/<domain>/.
packages/runner Headless Rust forge-runner CLI daemon for servers/CI; pairs as a device.
packages/contracts Shared cross-app TS types & registries, under packages/contracts/src/.
packages/observability Shared telemetry helpers (incl. the secret scrubber).

Commands

pnpm verify when you finish coding, before you push — the conformance entrypoint. Hooks only make it arrive sooner; a contributor with no plugin installed is held to exactly the same bar.

The gate is CI, not your laptop. verify declares the test suites and the build rather than running them; CI runs them, and main takes no merge whose ci-passed is red — the one required check.

Four jobs run after the merge, not before it — core-integration, whole-tree, images and the runner's macOS and Windows legs run on every push to a gated branch (main, dev) and nightly, and ci-passed does not need them (ISS-1370, priced in .forge/conformance.json $postMerge). A red there is fixed forward by the next run to land: read main's latest run before you push. To run them on a branch before it lands: gh workflow run CI --ref <branch> -f base=<the branch it lands on>.

Green covers the jobs that RAN. A skipped job passes ci-passed, and changes decides which run: read which ran, not the aggregate alone. A suite the filter should have selected and did not is the defect.

Read the full file on GitHub · 173 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.

  1. 29d ago Changed · +6 lines · +140 tokens per session d3b34e3b4ca1
  2. 1mo ago Changed · -11 lines · -217 tokens per session 207e13251a15
  3. 1mo ago Changed · -22 lines · -542 tokens per session c1907beb3b37
  4. 1mo ago Changed · -97 lines · -1,955 tokens per session e40b145f9643
  5. 1mo ago Changed · +4 lines · +115 tokens per session 1c6bcfd1f11d
  6. 1mo ago Changed · +1 lines · +47 tokens per session f617159563ba
  7. 1mo ago Changed · +15 tokens per session eb5776a1b1d7
  8. 1mo ago Changed · +21 lines · +395 tokens per session 9c03d7a5ff8f
  9. 1mo ago Changed · +10 lines · +134 tokens per session 236fdcead973
  10. 1mo ago First seen · 261 lines · 4,352 tokens per session scan A b6bce10c5e3e

Subscribe to this mod's changes

forge CLAUDE.md is an instructions file published in the GitHub repository SidCorp-co/forge (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,484 tokens to every session, about $0.0099 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-31.

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,750 tokens

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.

denoland/deno · 3,077 tokens