agentleFS
oktawianwybieralskioktawianwybieralski/coagent8/AGENTS.md

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…

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
  1. Distinctive:

    Before starting any task, read:

    line 3
  2. Very specific:

    Every file in .agents/rules/core/: the shared core rules from agent-standards, pinned in .agents/standards.lock.json.

    line 8

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

CoAgent8 - agent and contributor guidelines

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 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/)

RuleLevelScope
10 Architecture and runtimeP0Runtime reliability, schema validation, synchronized metadata, dependency and responsibility boundaries
11 Security and sandboxesP0Read-only profiles per backend, the delegate write profile, model cost governance and consent, secret redaction
12 Release workflowP0develop and X.Y.x lines, commit and PR conventions, versioning, npm channels, the release process, changelog, issues, repository settings, history recovery
13 ReviewP1The CoAgent8 review envelope and release candidate binding
14 Quality gateP1Additional check scopes, the test runner, provenance of bundles and artifacts, the full release gate
15 Cross-platformP2CI 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:

EarlierNow
00 core invariantscore rule 00 and project rule 10
01 security and sandboxesproject rule 11
02 Git workflowcore rule 02 and project rule 12 (same section numbers)
03 author and reviewercore rule 03 and project rule 13
04 quality gatecore rule 04 and project rule 14
05 cross-platformproject rule 15
06 language and stylecore rules 00 (keyboard characters) and 05

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.