agentmods.dev

COORD-Harness: Instructions file for Claude Code

CLAUDE.md

COORD-Harness CLAUDE.md is an instructions file for Claude Code from 0marm0/COORD-Harness. It costs 731 tokens per session, scanned A, a copy of COORD-Harness AGENTS.md, MIT.

Repository instructions for CoordHarness, a local system that coordinates work between multiple coding agents. They describe how agents start, claim, hand off, and finish tasks using a shared SQLite database.

In plain words
What is it for?
Starting and finishing coordinated work, claiming tasks, renewing temporary leases, retrieving limited context, handing work to another agent, and recording proof that a task is complete.
Why use it?
They give agents one reliable record of task ownership and progress, reducing conflicting edits, lost handoffs, and unclear completion status.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths.

This is 0marm0/COORD-Harness's own configuration. It tells Claude Code how to work on COORD-Harness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything COORD-Harness configures →

not rated 5repo changed 1mo ago A scan 731 tokens copy · 94% MIT
View source ↗ 0marm0/COORD-Harness
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/0marm0/COORD-Harness/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/0marm0/COORD-Harness

Made for: Claude Code.

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.

agentmods badge for COORD-Harness CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/0marm0/coord-harness/claude-md/github.svg)](https://agentmods.dev/instructions/0marm0/coord-harness/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/0marm0/coord-harness/claude-md"><img src="https://agentmods.dev/badge/instructions/0marm0/coord-harness/claude-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.

agentmods 80×15 button for COORD-Harness CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/0marm0/coord-harness/claude-md"><img src="https://agentmods.dev/badge/instructions/0marm0/coord-harness/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 731 This file is loaded in full into every session.
When invoked 731 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 94% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00731 $0.00731
Opus 5.5 $0.00292 $0.00292
Sonnet 5.5 $0.00146 $0.00146
Haiku 4.5 $0.00073 $0.00073

Measured 1mo ago against content hash f8ee364c3f35, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

COORD-Harness CLAUDE.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.

Origin

This is a copy

94% identical to COORD-Harness AGENTS.md — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 56 lines

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 Claude 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

  1. If .venv/bin/coord is 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 doctor exits 0, .venv/bin/coord onboard reports PASS, and MCP preflight returns query_core.mode="generic_coord_db" (docs/agent-onboarding.md §5, "Use the bounded MCP reads").
  2. Use the operating-coordharness repo skill at .claude/skills/operating-coordharness/, and the packaged commands in .claude/commands/, invoked as /coord-start.
  3. Run coord-start: it fixes one stable session identity, runs .venv/bin/coord onboard once, then MCP preflight. If the board is empty, use .venv/bin/coord create with a concrete repository-relative done_signal.
  4. Expand with bounded board, next_work, and work_context reads. Use the context lenses only when the active row needs broader history or source evidence.
  5. Claim before substantive work (coord-claim): check the row's done_signal and acceptance first, then renew only near lease expiry or a material milestone.
  6. Close with coord-close: complete only after the declared proof passes, otherwise park, block, or release with a resume contract. coord-handoff moves responsibility with exact row fences; coord-recover reconciles 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.

Read the full file on GitHub · 56 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.

  1. 1mo ago Changed · +17 lines · +277 tokens per session f8ee364c3f35
  2. 1mo ago First seen · 39 lines · 454 tokens per session scan A bfdf6d642c05

Subscribe to this mod's changes

COORD-Harness CLAUDE.md is an instructions file published in the GitHub repository 0marm0/COORD-Harness (5 stars, last pushed 3d ago), licensed MIT. It adds 731 tokens to every session, about $0.0029 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to COORD-Harness AGENTS.md, differing in 12 lines, and is treated as a copy.

Autonomous AgentsBuilding agentsClaude Codeagent-memoryagent-orchestrationai-agentscodex
Related

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

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,461 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,750 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens