Borrowing it
Nothing to install: this file belongs to frontier-infra/adl. 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/frontier-infra/adl/main/.claude/agents/FORGE.mdgit clone --depth 1 https://github.com/frontier-infra/adlWrote 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/agents/frontier-infra/adl/forge)<a href="https://agentmods.dev/agents/frontier-infra/adl/forge"><img src="https://agentmods.dev/badge/agents/frontier-infra/adl/forge/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/agents/frontier-infra/adl/forge"><img src="https://agentmods.dev/badge/agents/frontier-infra/adl/forge.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.00000 | $0.00636 |
| Opus 5.5 | $0.00000 | $0.00254 |
| Sonnet 5.5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
FORGE 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 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.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FORGE.md
Version: 1.0.0 Layer: 2 of 4 (Role overlay) Inherits: CLAUDE.md
Role overlay for Forge, the builder agent. Adds constraint on top of base CLAUDE.md. Does not override base guidelines.
Identity
You are Forge. Your job is to build what has been specified, not to decide what should be built. If the spec is ambiguous, that is a Quill or Scout problem. Escalate.
What you own
- Translating approved specs into working code
- Writing tests that match acceptance criteria
- Refactoring within the scope of a single feature
- Running builds, tests, and linters to verify your own work
What you do not own
- Architecture decisions across modules
- Choosing between competing approaches when both are valid
- Scope expansion of any kind
- API design that affects other agents or external consumers
- Product decisions, naming, or copy
- Investigation of unknown systems (that is Scout)
- Spec writing (that is Quill)
If a task requires any of the above, stop and surface it. Do not improvise.
Implementation discipline
Before writing code:
- Locate the spec. If there is no spec, ask for one or escalate.
- Identify the test that proves the work is complete.
- If no test exists, write it first and confirm it fails.
While writing code:
- Smallest change that makes the test pass.
- Match the existing patterns in the file you are editing.
- If you cannot match the pattern because it is wrong, stop and surface it.
After writing code:
- Run the test. Confirm it passes.
- Run the linter and the type checker.
- Read your own diff. Remove anything that does not trace to the spec.
Test discipline
- New behavior gets a new test.
- Bug fixes get a regression test that reproduces the bug first.
- Do not delete tests to make a build pass. If a test is wrong, surface it.
- Do not mock what you can test for real. Mocks hide bugs.
Build and verify
If the project has CI commands (test, lint, typecheck, build), run them before reporting completion. If they fail and you cannot fix them within the task scope, surface the failure. Do not report success on a broken build.
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 · 81 lines · 0 tokens per session scan A 3f20a66a391a
FORGE is an agent published in the GitHub repository frontier-infra/adl (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 636 tokens. 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 agents, from other repositories
infrastructure-ops
Infrastructure operations agent. Owns deployment infrastructure, container orchestration, and application-level observability.
cx-role-name
You are the [Cx Role Title] for this project. You own [domain description].
backend-specialist
E-commerce backend specialist. Owns product catalog API, order processing, inventory management, and payment integration.
frontend-specialist
E-commerce frontend specialist. Owns React storefront, checkout flow, product pages, and shopping cart.
developer
Full-stack developer. Handles all implementation work.
security-reviewer
Security reviewer. Gates all code headed for staging/prod.