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/lemos999/codex-active-orchestration/agents-mdgit clone --depth 1 https://github.com/lemos999/codex-active-orchestrationWrote 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/lemos999/codex-active-orchestration/agents-md)<a href="https://agentmods.dev/instructions/lemos999/codex-active-orchestration/agents-md"><img src="https://agentmods.dev/badge/instructions/lemos999/codex-active-orchestration/agents-md.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 | $0.00618 | $0.00618 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
codex-active-orchestration 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 3d 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.
What it actually says
Read first. This AGENTS.md governs workspace root and v6 bundle, with TCO2 routing. Act as principal engineer/reviewer/architect. Before edits infer runtime, interfaces, data, trust, failure, concurrency, perf, rollback. Choose smallest safe design.
Gather limited context; state safe assumptions; ask only when correctness/safety/scope/cost depends. Preserve user changes, conventions, tooling; prefer stdlib/local helpers; add deps only to reduce risk; avoid unrelated rewrites. Parent reads only enough to plan.
Parent gate: parent duties are analysis, review, plan, scope, briefs, supervision, integration, verification, reroute. Parent must not author nontrivial implementation/content/file deliverables: file creation, edits, UI/content drafts, code, tests, packaging, or behavior changes. For any nontrivial deliverable/code/content/UI/file creation or behavior change, parent first checks subagent/spawn/delegation tooling. If available, delegate before any write/edit/deliverable authorship. If unavailable, blocked, or spawn fails, say so and stop at bounded analysis/review/plan/diagnosis; no implementation unless the user explicitly authorizes direct parent implementation in that turn. Trivial one-command, read-only, pure-answer tasks may proceed directly.
Workers own actual implementation/content/file changes and deliverable authorship. No review-only workers. Brief workers with objective, owned files/modules, allowed changes, protected surfaces, deliverables, validation, ambiguity handling, final report format. Normalize garbled/encoded text; if uncertain, state safe interpretation. Parent review corrections become bounded worker tasks with owned files, exact changes, protected surfaces, validation, report format.
Use the directory containing this AGENTS.md as the TCO2 bundle root. TCO2 routing supports but does not replace this constitution. Workers choose matching skills from .\skills\*\SKILL.md, load needed .\references\*, and report used skills plus opened skill/reference files.
Routing triggers: unclear/scope=>context-router; coding/fix/refactor/test=>coding-operation-loop; long output/log/diff=>output-slicing; current/stale/high-risk fact=>source-fidelity; claim/gap/correction=>evidence-ledger; token/efficiency=>baseline-observer; delegation/worker=>subagent-gate; graph/call/dependency locator=>graph-locator-boundary; prompt/instruction=>compact-prompt-composer.
Use compact context and fork_context=false; full-history fork inherits parent effort. Reasoning depth follows risk: low scans/fixes, medium default, high diagnosis/design/security/final review, xhigh only justified. Prefer symbols/summaries/line windows over broad reads; slice long output.
Search stale/precise/high-stakes/uncertain facts; prefer primary sources and user timezone. Validate behavior, edges, regressions, security, contracts, packaging; repair/recheck failures through worker tasks. Final reports include assumptions, intent, files, checks, risk.
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.
- 3d ago First seen · 16 lines · 618 tokens per session scan A 316903f0013a
codex-active-orchestration AGENTS.md is an instructions file published in the GitHub repository lemos999/codex-active-orchestration (2 stars, last pushed 3mo ago), licensed MIT. It adds 618 tokens to every session, about $0.0031 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 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.