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/jdforsythe/forge/claude-mdgit clone --depth 1 https://github.com/jdforsythe/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/jdforsythe/forge/claude-md)<a href="https://agentmods.dev/instructions/jdforsythe/forge/claude-md"><img src="https://agentmods.dev/badge/instructions/jdforsythe/forge/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.00214 | $0.00214 |
| Opus 5 | $0.00107 | $0.00107 |
| Sonnet 5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
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 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.
What it actually says
Forge
An open-source system for science-backed AI team assembly.
Tech Stack
- Pure markdown skills and agent definitions (no framework dependency)
- Python scripts for packaging (package_skill.py)
- JSON for library index and usage tracking
Conventions
- All skill/agent files use YAML frontmatter
- Agent definitions follow the 7-component structure (see schemas/agent-definition.md)
- Team blueprints follow the blueprint format (see schemas/team-blueprint.md)
- SKILL.md files must be <500 lines; overflow goes in references/
- Reference files must be <300 lines with TOC if >150 lines
- File/folder names: kebab-case
- All research claims must cite sources
Key Principles
- Start simple, add complexity only when demonstrated need requires it
- Vocabulary routing is the primary generative-quality lever
- Real-world roles define scope, register, and decision boundaries
- 3-4 agents recommended, 5 maximum per team
- Structured artifacts for handoffs, not free-form dialogue
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 · 24 lines · 214 tokens per session scan A d4f9fdb47e1b
forge CLAUDE.md is an instructions file published in the GitHub repository jdforsythe/forge (151 stars, last pushed 2mo ago), licensed MIT. It adds 214 tokens to every session, about $0.0011 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.