Borrowing it
Nothing to install: this file belongs to albertbuchard/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/albertbuchard/forge/main/AGENTS.mdgit clone --depth 1 https://github.com/albertbuchard/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/albertbuchard/forge/agents-md)<a href="https://agentmods.dev/instructions/albertbuchard/forge/agents-md"><img src="https://agentmods.dev/badge/instructions/albertbuchard/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/albertbuchard/forge/agents-md"><img src="https://agentmods.dev/badge/instructions/albertbuchard/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.01118 | $0.01118 |
| Opus 5.5 | $0.00447 | $0.00447 |
| Sonnet 5.5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
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 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Forge
Scope
This file governs the projects/forge subtree and supplements the root AGENTS.md.
Branch rule
All Forge work must happen on main unless Albert explicitly asks for a different branch.
Do not create, switch to, or keep working on feature branches by default.
Before any Forge commit, verify git branch --show-current returns main.
Parent monorepo mirror rule
The Forge repository is the source of truth for files under projects/forge.
The parent monorepo may mirror Forge files, but parent merge resolution is not authoritative for Forge source.
- Do not let a parent-monorepo checkout, merge, or conflict resolution downgrade Forge files.
- If parent and Forge disagree, inspect Forge
mainfirst and restore from the Forge repository'sHEAD. - Before staging Forge release metadata, run
scripts/release/audit-release-guard.sh. - The local Forge pre-commit hook also runs the release guard. It fails if the working or staged iOS marketing version is older than the latest
ios-testflight-v*tag.
OpenClaw plugin rule
When Forge work involves the OpenClaw plugin, treat the repo-local plugin folder as the default install source.
- Before changing, reinstalling, restarting, or debugging Forge, OpenClaw, Hermes, or the Forge Codex adapter, verify the effective data root from explicit config and live runtime evidence. Do not infer the database from generic defaults.
- Check both config and runtime evidence when storage is in question: OpenClaw plugin config, Hermes Forge config,
FORGE_DATA_ROOT, and a live process/file-handle check such aslsof -p <forge-pid> | rg 'forge.sqlite|forge.json'. - Treat fallback locations such as
~/.forge, plugin extension folders, package-localdata/, and adapter-local data folders as candidates only until config or runtime evidence proves they are active. - Before any data-root repair, migration, restore, or merge, create a timestamped backup of every candidate Forge database and config file. Do not merge side databases into the selected canonical database unless an ID/content-level audit proves the side database contains relevant user data that is missing from that canonical database.
- Use the documented local-dev flow from
plugins/openclaw/README.md. - Prefer
openclaw plugins install ./projects/forge/plugins/openclaw, thenopenclaw plugins enable forge-openclaw-plugin, then repairplugins.allowif needed, thenopenclaw gateway restart, thenopenclaw forge health. - Do not switch to the published npm package or another global install path unless Albert explicitly asks for that.
- Do not change the Forge plugin
dataRootin~/.openclaw/openclaw.jsonunless Albert explicitly asks for a data-path change. - When verifying state, confirm
openclaw plugins info forge-openclaw-pluginreports the repo-local Forge plugin as the source path. - If Forge backend routes, the OpenClaw plugin package, onboarding contract, or Forge skill files changed, rebuild the plugin before verification so the running agent surface matches the source tree.
- After such changes, do not stop at static inspection. Rebuild, restart the OpenClaw gateway, then re-check
openclaw plugins info forge-openclaw-pluginandopenclaw forge health.
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 · 53 lines · 1,118 tokens per session scan A 3bf39b777d56
forge AGENTS.md is an instructions file published in the GitHub repository albertbuchard/forge (22 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,118 tokens to every session, about $0.0045 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.
forge AGENTS.md compared with instructions from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| forge AGENTS.mdalbertbuchard/forge | Instructions file | 22 | 1mo ago | Apache-2.0 | A | 1,118 | Codex, OpenCode |
| vscode buildNext.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 9,719 | GitHub Copilot |
| next.js AGENTS.mdvercel/next.js | Instructions file | 143k | yesterday | MIT | A | 7,461 | Codex, OpenCode |
| langchain AGENTS.mdlangchain-ai/langchain | Instructions file | 149k | yesterday | MIT | A | 4,680 | Codex, OpenCode |
| vscode oss-third-party-notices.instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 5,516 | GitHub Copilot |
| vscode copilot-instructions.mdmicrosoft/vscode | Instructions file | 195k | yesterday | MIT | A | 3,093 | GitHub Copilot |
| deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness | Instructions file | 274k | 2d ago | MIT | A | 4,313 | Codex, OpenCode |