Borrowing it
Nothing to install: this file belongs to zjio26/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/zjio26/forge/main/CLAUDE.mdgit clone --depth 1 https://github.com/zjio26/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/zjio26/forge/claude-md)<a href="https://agentmods.dev/instructions/zjio26/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/zjio26/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/zjio26/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/zjio26/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.01216 | $0.01216 |
| Opus 5.5 | $0.00486 | $0.00486 |
| Sonnet 5.5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00122 | $0.00122 |
Grade C, and why
forge CLAUDE.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.claude/agents/planner.md ~/.claude/agents/dev.md ~/.claude/agents/test.md ~/.claude/agents/learner.md ~/.claude/skills/forge How it starts
The opening of the file, as written. The whole thing — 101 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.
Project Overview
Forge is a Claude Code multi-agent collaborative development workflow distributed as a Claude Code plugin. It's not a traditional codebase — it's a collection of agent definitions (markdown files), a skill orchestrator, and a plugin manifest.
Architecture
Coordinator pattern: skills/forge/SKILL.md is the central orchestrator (Coordinator) that dispatches four specialized agents via the Agent tool. The Coordinator never reads intermediate file content — it only tracks paths and status to keep its context lean.
Coordinator (SKILL.md)
├── Planner (agents/planner.md) — sonnet, decomposes requirements into subtasks
├── Dev (agents/dev.md) — sonnet, implements + writes unit tests + fixes bugs
├── Test (agents/test.md) — haiku, unit tests (must pass) + integration tests (may skip)
└── Learner (agents/learner.md) — haiku, extracts lessons → knowledge base
Key flow: Planner → (Wave loop: Dev → Test → Fix) → Full Integration Test → Learner. State checkpointing (state.json) at every step enables crash recovery. The Coordinator resumes the same agent instances (via SendMessage + agentId) rather than creating new ones.
Wave-Based Processing
For large requirements with many subtasks, the workflow uses waves to prevent context overflow:
- Planner groups subtasks into waves based on dependency order (
waves.json) - Each wave gets a fresh Dev + Test agent pair
- Wave-level testing: unit tests + local integration only (no cross-wave business flows)
- Handoff: each Dev agent writes a handoff file (modified files, key interfaces, decisions) for the next wave
- Full integration test runs after all waves, using the complete unit + business test combo
- Small projects (single wave) run identically to the original flow — zero overhead
Test Layering
- Unit tests: must pass (no external deps). Dev agent writes them; Test agent verifies.
- Integration tests: best-effort. If skipped due to environmental constraints (network, hardware, etc.), it's informational only — does not cause overall FAIL.
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 · 101 lines · 1,216 tokens per session scan C c5931638544f
forge CLAUDE.md is an instructions file published in the GitHub repository zjio26/forge (11 stars, last pushed 5mo ago), licensed MIT. It adds 1,216 tokens to every session, about $0.0049 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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.