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/erewhon/forge/agents-mdgit clone --depth 1 https://github.com/erewhon/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.00410 | $0.00410 |
| Opus 5 | $0.00205 | $0.00205 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
forge AGENTS.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 yesterday.
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 — agent notes
Front door for the erewhon code agents: the forge CLI and forge-mcp MCP server over the
agent packages in forge/<package>/. Human-facing docs live in README.md; per-package
READMEs cover each agent.
Conventions
- Python 3.12+, uv-managed. Run everything through
uv run ...from the repo root. - Tests:
uv run pytest forge/<package>for one package,uv run pytestfor the suite. - Lint/format:
uv run ruff check .anduv run ruff format .(line length 100). - Typed code with pydantic models throughout. Settings are pydantic-settings classes with
per-agent env prefixes; a
.envat the repo root holds machine-local values and is never committed. - Nous integration is optional (the
[nous]extra). Anything touching it must import lazily/guarded — seeforge/shared/task_store.pyandforge/task_worker/nous_client.pyfor the pattern.TASK_STORE_BACKEND=githubmust always work without nous installed. - Pure signal/parse helpers stay separate from network fetchers, and fetchers are injectable
for tests (see
forge/dependabot/supply_chain.py). - Write errors for the next attempt, not the stack-trace reader: any error on a path a loop
retries (worker outcomes, task-store writes, dispatch preflight, executor failures) must state
the failed expectation and the likely remedy, then the evidence — never a bare status or
exception. See
docs/error-surface-audit.md.
Boundaries for autonomous workers
- Do not modify
.task_worker/or anything inside it (worker plumbing and task specs). - Do not commit
.envor log files. - Keep the diff scoped to the files named in the task spec.
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.
- yesterday First seen · 30 lines · 410 tokens per session scan A 6b77162a2d97
forge AGENTS.md is an instructions file published in the GitHub repository erewhon/forge (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 410 tokens to every session, about $0.0020 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-31.
Other instructions, from other repositories
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.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit 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.
langchain 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.