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/alirezarezvani/claudeforge/claude-mdgit clone --depth 1 https://github.com/alirezarezvani/ClaudeForgeWrote 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/alirezarezvani/claudeforge/claude-md)<a href="https://agentmods.dev/instructions/alirezarezvani/claudeforge/claude-md"><img src="https://agentmods.dev/badge/instructions/alirezarezvani/claudeforge/claude-md.svg" alt="Measured on agentmods" 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 | $0.00964 | $0.00964 |
| Opus 5 | $0.00482 | $0.00482 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
ClaudeForge 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Top-level guidance for Claude Code when working on this repository.
Project Overview
ClaudeForge is a Claude Code plugin (manifest at .claude-plugin/plugin.json) and standalone toolkit for the CLAUDE.md lifecycle: initialise, enhance, sync, and modularise files with a hard 150-line cap, automatic chaining via @path imports, and Karpathy behavioural guardrails. Works in any Claude Code or Claude.cowork project.
Five components ship in this repo:
- Skill (
claudeforge-skill, inskill/) — Python modules for analysis, generation, validation. Enforces the 150-line cap. - Slash command (
/enhance-claude-md, incommand/) — interactive init/enhance workflow. Delegates deep codebase scans to the Explore subagent. - Slash command (
/sync-claude-md, incommand/) — walks every CLAUDE.md, prunes stale references, enforces the 150-line cap, repairs the root ↔ sub chain. - Guardian agent (
claude-md-guardian, inagent/) — background sync triggered bySessionStart/PreToolUse/PostToolUsehooks. - Karpathy guidelines skill (
karpathy-guidelines, inskill/karpathy-guidelines/) — behavioural guardrails embedded into every generated CLAUDE.md. Adapted with attribution from the MIT-licensed forrestchang/andrej-karpathy-skills repo.
Current version: 2.1.0 — see CHANGELOG.md. v1 → v2 upgrade: docs/MIGRATION_V2.md.
Quick Navigation
- Skill development
- Slash command development
- Guardian agent development
- Installation, testing & release
Chained context (Claude Code auto-imports these):
@skill/CLAUDE.md @command/CLAUDE.md @agent/CLAUDE.md @docs/CLAUDE.md
Behavioral Guidelines
Behavioural guardrails applied to every coding, review, and refactoring task in this repo. Full skill: ~/.claude/skills/karpathy-guidelines/SKILL.md.
- Think before coding. State load-bearing assumptions; if a request has multiple reasonable interpretations, surface them instead of picking silently. Stop and ask when something is genuinely unclear.
- Simplicity first. Write the minimum code that solves the stated problem. No speculative abstractions, no unrequested configuration, no error handling for conditions that cannot occur.
- Surgical changes. Touch only what the task requires. Match surrounding style. Every changed line should trace directly to the user's request.
- Goal-driven execution. Convert vague requests into verifiable success criteria before coding (failing test first), and state a step-by-step plan with per-step verification for multi-step work.
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 First seen · 71 lines · 964 tokens per session scan A 320a12e83ddc
ClaudeForge CLAUDE.md is an instructions file published in the GitHub repository alirezarezvani/ClaudeForge (424 stars, last pushed 3mo ago), licensed MIT. It adds 964 tokens to every session, about $0.0048 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
toh-framework CLAUDE.md
Claude Code instructions for wasintoh/toh-framework, covering claude.md — toh framework (repo development guide), what this is, everyday commands, verification protocol and single source, transformed per ide.
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.
claude-code-templates CLAUDE.md
Claude Code instructions for Justdvp/claude-code-templates, covering claude.md, project overview, development commands, package management and application commands.
deckforge AGENTS.md
Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.
coordinate-agents AGENTS.md
AGENTS.md instructions for hogancv/coordinate-agents, covering repository instructions for ai contributors, canonical identity, repository map, required checks and change rules.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.