Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/jayminwest/warren/agents-mdgit clone --depth 1 https://github.com/jayminwest/warrenWhat 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 | $0.10174 | $0.10174 |
| Opus 5 | $0.05087 | $0.05087 |
| Sonnet 5 | $0.02035 | $0.02035 |
| Haiku 4.5 | $0.01017 | $0.01017 |
Grade A, and why
warren 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 yesterday.
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 — 822 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is the canonical instruction doc for AI coding agents working
in this repo, following the agents.md convention.
CLAUDE.md is a symlink to this file, so one document serves every
harness and there is nothing to drift.
What this project is
Coding agents are tools. Warren turns them into infrastructure.
It runs agent harnesses as isolated workloads on infrastructure the operator controls. Warren owns the workspace, lifecycle, limits, events, intervention, recovery, and Git delivery.
AgentRuntimeAdapter keeps the kernel harness-neutral. A harness needs
an adapter before the runtime can drive it. The current distribution
ships Pi and Claude Code adapters.
Runtime providers place each run in a local bwrap sandbox on Linux or
sandbox-exec sandbox on macOS, a sibling Docker container, or a
Kubernetes pod.
The kernel guarantees a pushed workspace branch. Project settings can add PR creation and tracker reactions around that boundary.
The fresh-install path is standalone. A user with a GitHub URL and the model credential for a shipped harness can dispatch a run end-to-end with no other os-eco tooling. Around that kernel, two os-eco data-plane tools integrate as opt-in features, not required infrastructure.
- mulch — persistent agent memory across runs. Activated by a
.mulch/directory in the project. - seeds — the integrated issue queue agents read from and write to.
Activated by a
.seeds/directory. Seeds is implementation #1 of theIssueTrackerseam (src/tracker/contract.ts), with external trackers reachable through theRemoteTrackerbridge — see docs/design/issue-tracker.md.
The agent registry is entirely inline. BUILTIN_AGENTS
(src/registry/builtins/) ships seven agents and boot seeds them into
the agents table on every start: claude-code, pi,
planner, nightwatch, bugwatch, pr-fixer, and healer. There is
no external agent library. GET /agents still reports
source: "builtin" | "library" provenance. The library arm survives
only for legacy rows.
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.
- yesterday First seen · 822 lines · 10,174 tokens per session scan A c0cc40ae2db7
warren AGENTS.md is an instructions file published in the GitHub repository jayminwest/warren (346 stars, last pushed 3d ago), licensed MIT. It adds 10,174 tokens to every session, about $0.0509 per session on Opus 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.
Other instructions, from other repositories
factory CLAUDE.md
Instructions for watt-mind/factory: Claude, please refer to AGENTS.md and docs/protocol.md for the primary repository context, architecture, commands, operational rules, and tracker issue management standards.
factory GEMINI.md
Instructions for watt-mind/factory: Gemini, please refer to AGENTS.md and docs/protocol.md for the primary repository context, architecture, commands, operational rules, and tracker issue management standards.
factory AGENTS.md
Instructions for watt-mind/factory, covering commands, agent operating floor, handoff, never auto-merge and protected branches.
zeroshot CLAUDE.md
Claude Code instructions for the-open-engine/zeroshot, covering zeroshot: multi-agent coordination engine, 🔴 critical rules, 🔴 general purpose requirement (critical), 🔴 behavioral standards and where to look.
dev-3.0 AGENTS.md
Instructions for h0x91b/dev-3.0, covering agents.md, response style, what is this, ui/ux work — which skill, and when (mandatory) and where dev3 overrides the better-family skills.
zeroshot AGENTS.md
AGENTS.md instructions for the-open-engine/zeroshot, covering zeroshot: multi-agent coordination engine, critical rules, where to look, cluster worker contracts and cli quick reference.