Borrowing it
Nothing to install: this file belongs to 0marm0/COORD-Harness. 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/0marm0/COORD-Harness/main/AGENTS.mdgit clone --depth 1 https://github.com/0marm0/COORD-HarnessWrote 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/0marm0/coord-harness/agents-md)<a href="https://agentmods.dev/instructions/0marm0/coord-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/0marm0/coord-harness/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/0marm0/coord-harness/agents-md"><img src="https://agentmods.dev/badge/instructions/0marm0/coord-harness/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.00727 | $0.00727 |
| Opus 5.5 | $0.00291 | $0.00291 |
| Sonnet 5.5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
COORD-Harness 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- COORD-Harness CLAUDE.md — 94% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoordHarness agent entrypoint
COORDHARNESS_AGENT_INSTRUCTION_SENTINEL=v1
CoordHarness coordinates multi-agent work through one local SQLite authority. coord.db
owns work, claims, leases, handoffs, and lifecycle events. Markdown provides stable
orientation only; dashboards, job sidecars, knowledge.db, facts, KFTS, and accepted
memory are evidence or recall, never lifecycle state.
Start and finish
- If
.venv/bin/coordis missing, run./scripts/setup.sh, then restart this session — the checked-in MCP launcher (scripts/coord-mcp-launch.sh) fails closed with that same instruction instead of a raw ENOENT. Setup is done when.venv/bin/coord doctorexits0,.venv/bin/coord onboardreportsPASS, and MCPpreflightreturnsquery_core.mode="generic_coord_db"(docs/agent-onboarding.md§5, "Use the bounded MCP reads"). - Use
$operating-coordharness(repo skill:.agents/skills/operating-coordharness/), and the packaged commands in.agents/commands/, invoked as$coord-start. - Run
coord-start: it fixes one stable session identity, runs.venv/bin/coord onboardonce, then MCPpreflight. If the board is empty, use.venv/bin/coord createwith a concrete repository-relativedone_signal. - Expand with bounded
board,next_work, andwork_contextreads. Use the context lenses only when the active row needs broader history or source evidence. - Claim before substantive work (
coord-claim): check the row'sdone_signaland acceptance first, then renew only near lease expiry or a material milestone. - Close with
coord-close: complete only after the declared proof passes, otherwise park, block, or release with a resume contract.coord-handoffmoves responsibility with exact row fences;coord-recoverreconciles a row the board is wrong about.
Do not edit SQLite or lifecycle projections by hand. Preserve unrelated dirty work and never weaken identity, proof, review, or authority checks to make a transition pass.
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.
- 1mo ago Changed · +18 lines · +276 tokens per session cdf1e8a0feec
- 1mo ago First seen · 38 lines · 451 tokens per session scan A a9f1341a8b35
COORD-Harness AGENTS.md is an instructions file published in the GitHub repository 0marm0/COORD-Harness (5 stars, last pushed 3d ago), licensed MIT. It adds 727 tokens to every session, about $0.0029 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.