Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/tt-wang/forge/claude-mdgit clone --depth 1 https://github.com/TT-Wang/forgeWhat 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 | $0.00434 | $0.00434 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00043 | $0.00043 |
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 2d 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.
What it actually says
Forge
Forge is a lightweight workflow layer for Claude Code that adds structured planning, deep validation, retry intelligence, session resumability, and cross-session memory.
Quick Start
/forge <objective>
This triggers the full workflow: understand → plan → validate plan → execute → validate → retry → learn.
Skills
/forge <objective>— Full workflow: plan, execute, validate, learn/forge-validate <module-id>— Validate a specific module/forge-status— Show current plan status and memory
Agents
planner— Decomposes objectives into module DAGs, validates plan structureworker— Executes a single module in a worktreereviewer— Reviews completed modules for correctness, uses contract checksdebugger— Root-cause analysis with structured log inspection
MCP Tools
The forge MCP server provides 7 tools:
validate— Run verification commands with syntax checks, API contract verification, stagnation/velocity/oscillation detectionvalidate_plan— Structural plan validation: DAG cycles, file overlaps, command existence, schema checksmemory_recall— Search project/global memorymemory_save— Save learned patternsiteration_state— Track retry attempts per moduleforge_logs— Query structured JSONL logs (filter by run, module, phase, severity)session_state— Save/load/list orchestrator state for session resumability
Plugin Structure
This project is a Claude Code plugin. Install with claude plugin add github:TT-Wang/forge.
agents/ — Agent definitions (planner, worker, reviewer, debugger)
skills/ — Skill definitions (/forge, /forge-validate, /forge-status)
forge-mcp-server/ — MCP server (7 tools: validate, validate_plan, memory, iteration, logs, session)
.claude-plugin/ — Plugin manifest (plugin.json)
.forge/ — Runtime data (plans, memory, iterations, logs, state)
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.
- 2d ago First seen · 48 lines · 434 tokens per session scan A 79b64d90c4b6
forge CLAUDE.md is an instructions file published in the GitHub repository TT-Wang/forge (35 stars, last pushed 2mo ago), licensed MIT. It adds 434 tokens to every session, about $0.0022 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-08-30.
Other instructions, from other repositories
ii-agent AGENTS.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent contributor guide, quick start, repository map, mandatory rules and architecture.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).
crust AGENTS.md
Instructions for chenxin-yan/crust, covering tests, documentation, changesets, agent skills and issue tracker.
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.
TuyaOpen AGENTS.md
AGENTS.md instructions for tuya/TuyaOpen, covering agents.md, cursor cloud specific instructions, communication and behavior, environment setup and export progress protocol (ide).