What is foremerge AGENTS.md?

Repository instructions for Foremerge, a local coordination system for parallel coding agents. It describes the project's branch, pull-request, release, deployment, and data-safety rules.

Use it as the operating guide when contributing to Foremerge, coordinating agents, opening changes for review, or handling releases and deployments.

It gives agents the repository-specific constraints they need to avoid unsafe development builds, unreviewed changes, and incorrect release or deployment actions.

How naw103/foremerge configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to naw103/foremerge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/naw103/foremerge/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/naw103/foremerge

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/naw103/foremerge/agents-md/github.svg)](https://agentmods.dev/instructions/naw103/foremerge/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/naw103/foremerge/agents-md"><img src="https://agentmods.dev/badge/instructions/naw103/foremerge/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/naw103/foremerge/agents-md"><img src="https://agentmods.dev/badge/instructions/naw103/foremerge/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,087 This file is loaded in full into every session.

When invoked 2,087 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02087	$0.02087
Opus 5.5	$0.00835	$0.00835
Sonnet 5.5	$0.00417	$0.00417
Haiku 4.5	$0.00209	$0.00209

Measured 12d ago against content hash 4a1ea9f38a44, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

foremerge 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 12d 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.

AGENTS.md · 156 lines

How it starts

The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Foremerge: guide for coding agents

Foremerge is a local, Git-compatible coordination layer for parallel coding agents: a CLI, an MCP server and a loopback JSON API over one SQLite ledger per repository. This file is the short version for an agent working in this repository; CLAUDE.md imports it. CONTRIBUTING.md is the full contributor guide and docs/RELEASING.md is the release checklist.

The repository is public. Everything tracked here is published.

Rules

Changes reach main through a reviewed pull request. Work on a branch or a fork and open a pull request. Tagging, releases, registry publishing and the website are the maintainer's: a pushed v* tag starts the release workflow and a push to gh-pages publishes foremerge.com. See How releases and deploys run.
Never run a development build against a real repository. A development build can leave a ledger at a schema no released binary reads: it creates a new ledger at its own schema, ledger migrate and ledger reset move an existing one to it, and releases up to 0.5.1 migrated any ledger they opened, one way. Every released binary then refuses that ledger. That covers target/debug/foremerge, target/release/foremerge, the fmg twins and cargo run. --cwd defaults to the current directory, so a run from inside another repository acts on that repository's ledger. Use the test suite, which works in temporary directories, or a throwaway repository with --cwd and --database both pointing at it. Never cargo install --path . and never point an agent client's configuration at target/.
A ledger is the user's data. Do not delete, move, reset, migrate or hand-edit <git-common-dir>/foremerge/state.sqlite3. To inspect one, skip the CLI and open it read-only: sqlite3 "file:<path>?mode=ro" "select ...". If the Foremerge MCP server reports that it is unavailable, say so and leave the fix to the user.
Nothing private in tracked files. The repository is public: no secrets, tokens, internal hostnames, private process notes, generated databases or .foremerge state.
Some paths need the maintainer's review. .github/CODEOWNERS lists them: the agent guides and client integration, CI and the release workflow, distribution, the ledger and acceptance gate, and authentication. If a change touches one, say so in the pull request.

Read the full file on GitHub · 156 lines

Changes

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.

12d ago First seen · 156 lines · 2,087 tokens per session scan A 4a1ea9f38a44

Subscribe to this mod's changes

foremerge AGENTS.md is an instructions file published in the GitHub repository naw103/foremerge (462 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,087 tokens to every session, about $0.0083 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-10-25.

Git and workflow Project management Releases ai-agents cli coding-agents developer-tools mcp

foremerge AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
foremerge AGENTS.mdnaw103/foremerge	Instructions file	462	yesterday	Apache-2.0	A	2,087	Codex, OpenCode
skill-doctor github-automation.instructions.mdevilstar2016/skill-doctor	Instructions file	16	7d ago	MIT	A	72	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	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

foremerge: Instructions file for Codex