Borrowing it
Nothing to install: this file belongs to icohangar-ops/agent-conductor. 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/icohangar-ops/agent-conductor/main/AGENTS.mdgit clone --depth 1 https://github.com/icohangar-ops/agent-conductorWrote 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/icohangar-ops/agent-conductor/agents-md)<a href="https://agentmods.dev/instructions/icohangar-ops/agent-conductor/agents-md"><img src="https://agentmods.dev/badge/instructions/icohangar-ops/agent-conductor/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/icohangar-ops/agent-conductor/agents-md"><img src="https://agentmods.dev/badge/instructions/icohangar-ops/agent-conductor/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.00762 | $0.00762 |
| Opus 5.5 | $0.00305 | $0.00305 |
| Sonnet 5.5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
agent-conductor 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Agent Conductor
Guidance for AI coding agents working in this repository. (Yes — Conductor's
own contract compiles with Conductor: contract_load on this file.)
Mission
Agent Conductor turns AGENTS.md operating manuals and SKILL.md skills into an active orchestration layer over MCP, with the Consensus Hardening Protocol gating high-stakes decisions. Agents should keep the parser lossless, the dependency surface near zero, and the MCP stdout stream protocol-clean.
Architecture
| Layer | Role | Do | Don't |
|---|---|---|---|
src/contract/ |
Contract compilation | Extract recognized AGENTS.md patterns; preserve unknown sections | Drop content the parser doesn't understand |
src/contract/workspace.ts |
Multi-root compile | Walk declared roots; merge layer tables and gates; fail closed | Invent or skip a root the map declared |
src/skills/ |
Skill discovery | Frontmatter-only metadata on discovery; bodies on demand | Load bodies eagerly |
src/budget/ |
Bounded-run spend control | Fail-closed ceilings, ledger before/after, compose CHP R0 | Invent a parallel policy engine or a new package |
src/engine/ + engine/bridge.py |
Decision engine boundary | Speak newline-delimited JSON over child stdio | Print logs to stdout on either side |
engine/vendor/cme/ |
Vendored CHP core | Keep byte-identical to upstream except __init__.py |
Edit vendored logic — fix upstream instead |
test/ |
Regression guard | Test against the real example fixture | Mock the Python engine in engine tests |
Engineering rules
Non-negotiables
- stdout is sacred — MCP transport owns process stdout; all logging goes to stderr on both sides of the bridge.
- Zero new runtime dependencies — markdown/frontmatter parsing stays hand-rolled; only the MCP SDK and zod are allowed.
- Lossless compilation — unrecognized AGENTS.md sections must survive into
contract.sections. - Erasable TypeScript only — source must run under Node's type stripping (no enums, no parameter properties);
tsconfigenforceserasableSyntaxOnly. - Vendor discipline —
engine/vendor/cme/is upstream's code; changes belong upstream or inbridge.py. - Engine runs on stdlib Python 3.9+ — no pip installs in the engine path.
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 · -1 lines · -16 tokens per session c7108eb15d23
- 1mo ago Changed · +22 lines · +162 tokens per session 156f024646df
- 1mo ago Changed · +10 tokens per session 7e0381cb393b
- 2mo ago First seen · 56 lines · 606 tokens per session scan A 483e6df9771a
agent-conductor AGENTS.md is an instructions file published in the GitHub repository icohangar-ops/agent-conductor (0 stars, last pushed 25d ago), licensed MIT. It adds 762 tokens to every session, about $0.0030 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.