Borrowing it
Nothing to install: this file belongs to LucasDuys/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/LucasDuys/forge/main/AGENTS.mdgit clone --depth 1 https://github.com/LucasDuys/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/lucasduys/forge/agents-md)<a href="https://agentmods.dev/instructions/lucasduys/forge/agents-md"><img src="https://agentmods.dev/badge/instructions/lucasduys/forge/agents-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/lucasduys/forge/agents-md"><img src="https://agentmods.dev/badge/instructions/lucasduys/forge/agents-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.01215 | $0.01215 |
| Opus 5.5 | $0.00486 | $0.00486 |
| Sonnet 5.5 | $0.00243 | $0.00243 |
| Haiku 4.5 | $0.00121 | $0.00121 |
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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge — Agent Routing
This file tells Claude Code how to route work to the correct specialized agent when working on the Forge project.
Agent Definitions
forge-speccer
When to use: During /forge brainstorm — writing specs from user input, existing code, or docs.
Files it owns: skills/brainstorming/SKILL.md, templates/spec.md
Key behavior: Asks clarifying questions one at a time, proposes approaches, writes R-numbered specs with testable acceptance criteria.
forge-planner
When to use: During /forge plan — decomposing specs into task frontiers.
Files it owns: skills/planning/SKILL.md, templates/plan.md
Key behavior: Reads specs, builds dependency DAGs, groups tasks into parallelizable tiers, estimates tokens per task, tags tasks with repo ownership.
forge-executor
When to use: During /forge execute — implementing individual tasks.
Files it owns: skills/executing/SKILL.md
Key behavior: Reads task from frontier, implements with TDD if available, runs tests, commits atomically. Follows inner loop: implement → test → fix → review → fix → commit.
forge-reviewer
When to use: After task implementation (standard/thorough depth) — code review against spec.
Files it owns: skills/reviewing/SKILL.md, references/review-protocol.md
Key behavior: Reviews actual code (not the report), checks against spec requirements, flags missing pieces and over-engineering. Returns PASS or ISSUES with file:line references.
forge-verifier
When to use: After all tasks in a phase/spec complete — goal-backward verification.
Files it owns: references/backprop-patterns.md
Key behavior: Checks observable truths (not task checkboxes), detects stubs/placeholders, verifies cross-component wiring. Returns PASSED or GAPS_FOUND.
forge-researcher
When to use: Before complex/unfamiliar tasks during /forge execute — research before implementation.
Files it owns: None (produces ephemeral research reports)
Key behavior: Multi-source research: official docs (Context7), codebase conventions, security best practices, knowledge graph queries. Returns structured research reports with source citations.
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.
- 1mo ago First seen · 93 lines · 1,215 tokens per session scan A a589345b5744
forge AGENTS.md is an instructions file published in the GitHub repository LucasDuys/forge (56 stars, last pushed 3mo ago), licensed MIT. It adds 1,215 tokens to every session, about $0.0049 per session on Opus 5.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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
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).