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 skills/0marm0/coord-harness/operating-coordharnessnpx skills add 0marm0/COORD-Harness --skill operating-coordharnessgit 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/skills/0marm0/coord-harness/operating-coordharness)<a href="https://agentmods.dev/skills/0marm0/coord-harness/operating-coordharness"><img src="https://agentmods.dev/badge/skills/0marm0/coord-harness/operating-coordharness.svg" alt="Measured on agentmods" 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.00070 | $0.00618 |
| Opus 5 | $0.00035 | $0.00309 |
| Sonnet 5 | $0.00014 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
operating-coordharness 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating CoordHarness
Use one coord.db as lifecycle authority. Treat dashboards, native clients,
sidecars, documentation, and memory as projections or evidence; none may
silently change lifecycle state.
Start from the smallest truthful context
- Resolve the coordinated project root and database explicitly. Do not infer a database from an unrelated checkout.
- Run
coord preflightwhen available; otherwise inspectcoord boardand the exact work item before loading broad project context. - Claim an existing assignable item before substantive work. If new work is
genuinely required, create it with an acceptance condition and concrete
done_signalbefore claiming it.
Read references/lifecycle.md for the lifecycle, handoff, review, and completion-proof contract.
Keep parallel work bounded
The orchestrator owns the durable claim. Give each subagent a non-overlapping objective and file scope; record its bounded result under the parent instead of minting misleading peer ownership. Use typed handoff when responsibility moves between actors, and optimistic concurrency when the row may have changed.
Separate agent turns from durable processes
Use tracked jobs for long CPU, GPU, build, indexing, or local-model work. A job publishes compact liveness and progress; its command body, prompts, stdout, credentials, and source text do not belong in the sidecar or board.
Read references/jobs.md before launching or terminating a process, especially when a GPU lock or process-group cleanup is involved.
Expand context intentionally
Exact board state and source artifacts outrank capsules, search indexes, facts, and accepted memory. Begin with the bounded capsule, follow exact pointers for the active item, and expand only the plane that answers the current question.
Read references/context.md when using context federation, facts, graph traversal, memory proposals, or fresh-session continuation.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 64 lines · 70 tokens per session scan A d7c7264fde29
operating-coordharness is a skill published in the GitHub repository 0marm0/COORD-Harness (1 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 618 once invoked, about $0.0003 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-31.
Other skills, from other repositories
with-frontmatter
Help an agent inspect a failed trace run, identify likely failure layers, and produce a short audit note.
os-eco-dep-sync
Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR. Use when checking if warren is on the newest burrow/plot/canopy/seeds/mulch/sapling.
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
prep
Session wrap-up. Update memories, check plans, review git state, check inbox, flag loose ends. Use before closing a session or compacting context.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries.
system_status
Check system health -- disk usage, memory, running processes, uptime.