coagent8
AGENTS.md2 starsChanged 11 days agoMITView on GitHub
Before starting any task, read: 1. .agents/project.md: the project parameters (branches, languages, primary sources, reviewers, standing go-aheads, commands). 2. Every file in .agents/rules/core/: the shared core rules from agent-standards, pinned in .agents/standards.lock.json. They are copied verbatim and never edited here; node .agents/standards/agent-standards.mjs check verifies the copy. 3. The project rules below that apply to the task. Precedence: the owner's instructions and the environment's limits, then the core rules (P0 before P1 before P2), then the project rules and .agents/project.md, then…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 33,315 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository10 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- coagent8-workflowSkill
- pr-mergeSkill
- coagent8-consultSkill
- coagent8-delegateSkill
- coagent8-doctorSkill
- coagent8-issueSkill
- coagent8-loopSkill
- coagent8-reviewSkill
- coagent8-sessionSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Before starting any task, read:
- Very specific: line 8
Every file in .agents/rules/core/: the shared core rules from agent-standards, pinned in .agents/standards.lock.json.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CoAgent8 - agent and contributor guidelines
Before starting any task, read:
.agents/project.md: the project parameters (branches, languages, primary sources, reviewers, standing go-aheads, commands).- Every file in
.agents/rules/core/: the shared core rules from agent-standards, pinned in.agents/standards.lock.json. They are copied verbatim and never edited here;node .agents/standards/agent-standards.mjs checkverifies the copy. - The project rules below that apply to the task.
Precedence: the owner's instructions and the environment's limits, then the
core rules (P0 before P1 before P2), then the project rules and
.agents/project.md, then skills. A project rule may tighten a core rule; it
never relaxes one. When two requirements contradict each other, state the
conflict and stop the dependent work.
Project and documents
GitHub Issues hold the backlog: every planned result is an issue,
and a milestone names its release (owner decision 2026-11-05,
project.md). Use
docs/ROADMAP.md for the direction and the order of the
milestones, and docs/ARCHITECTURE.md for contracts and
design. These are the two active project documents; optional ignored local notes
are not instructions. Current work and evidence are in issues and PRs: do not add
a document that an issue or a PR can hold (owner decision 2026-11-05).
The product is a client-independent system for delegating complete tasks to
cooperating agents (owner decision, 2026-10-08). Roles and model/provider choices are independent;
client skill installation is planned. The current runtime is a read-only
MCP-to-CLI bridge except delegate, whose workspace-write profile follows
rule 11 (owner decision
2026-10-21), until verified task execution profiles land. Follow the roadmap's
full coagent direction while preserving audit gates and quiet desktop
operation. Historical plans and RFCs do not override this direction.
Project rules (.agents/rules/)
| Rule | Level | Scope |
| 10 Architecture and runtime | P0 | Runtime reliability, schema validation, synchronized metadata, dependency and responsibility boundaries |
| 11 Security and sandboxes | P0 | Read-only profiles per backend, the delegate write profile, model cost governance and consent, secret redaction |
| 12 Release workflow | P0 | develop and X.Y.x lines, commit and PR conventions, versioning, npm channels, the release process, changelog, issues, repository settings, history recovery |
| 13 Review | P1 | The CoAgent8 review envelope and release candidate binding |
| 14 Quality gate | P1 | Additional check scopes, the test runner, provenance of bundles and artifacts, the full release gate |
| 15 Cross-platform | P2 | CI matrix, hidden Windows launches, process teardown, buffer bounds, Node 24 build |
Skills for contributors are in .agents/skills/.
Earlier rule numbers
Documents and history written before 2026-10-31 cite the earlier rule files:
| Earlier | Now |
| 00 core invariants | core rule 00 and project rule 10 |
| 01 security and sandboxes | project rule 11 |
| 02 Git workflow | core rule 02 and project rule 12 (same section numbers) |
| 03 author and reviewer | core rule 03 and project rule 13 |
| 04 quality gate | core rule 04 and project rule 14 |
| 05 cross-platform | project rule 15 |
| 06 language and style | core rules 00 (keyboard characters) and 05 |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

