Borrowing it
Nothing to install: this file belongs to jleechanorg/agent-orchestrator-ts. 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/jleechanorg/agent-orchestrator-ts/main/AGENTS.mdgit clone --depth 1 https://github.com/jleechanorg/agent-orchestrator-tsWrote 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/jleechanorg/agent-orchestrator-ts/agents-md)<a href="https://agentmods.dev/instructions/jleechanorg/agent-orchestrator-ts/agents-md"><img src="https://agentmods.dev/badge/instructions/jleechanorg/agent-orchestrator-ts/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/jleechanorg/agent-orchestrator-ts/agents-md"><img src="https://agentmods.dev/badge/instructions/jleechanorg/agent-orchestrator-ts/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.04518 | $0.04518 |
| Opus 5.5 | $0.01807 | $0.01807 |
| Sonnet 5.5 | $0.00904 | $0.00904 |
| Haiku 4.5 | $0.00452 | $0.00452 |
Grade A, and why
agent-orchestrator-ts 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 9d 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Orchestrator — Agent & Contributor Guidelines
This file guides AI coding agents (Claude Code, Codex, Cursor, etc.) working on this codebase.
Development Hierarchy — How to Add Capabilities
Before writing any code, ask: "Can I achieve this without changing core?"
Follow this order strictly:
1. Dispatch an AO Worker (default — almost always)
When given a task, dispatch an AO worker first — not claude -p, not manual investigation, not a one-off script. AO workers are the standard execution model for all work in this repo.
# General task
ao spawn "fix the rate limit handler in scm-github"
# On a specific PR
ao spawn --project agent-orchestrator --claim-pr <N>
# On a bead
ao spawn --project agent-orchestrator --bead bd-xxx
AO workers are general-purpose. They are not limited to claiming PRs — a worker can do any task. Only fall back to direct CLI (claude -p, claude --print) for quick one-liners, diagnostics, or when AO is genuinely unavailable.
AO usage skill: skills/agent-orchestrator/SKILL.md
bash scripts/setup.shinstalls this repo skill into~/.claude/skills/agent-orchestratorand~/.codex/skills/agent-orchestrator.- Read it when you need the concrete AO command workflow instead of improvising session management.
2. Use Config First
Check whether agent-orchestrator.yaml already supports what you need:
reactions— add/override event reactions (ci-failed, changes-requested, agent-stuck, etc.)agentRules— per-project or global instructions injected into agent system promptsnotificationRouting— control which notifiers receive which priority levelsdefaults— set default runtime, agent, workspace, notifiersprojects[*].agentConfig— per-project model, permissions, environment
If the config surface can express the behavior, stop here. No code needed.
3. Make a New Plugin (existing plugin slot)
If config is not enough, implement a plugin using an existing slot:
runtime— how sessions run (tmux, docker, etc.)agent— how to talk to an AI agent (claude-code, codex, cursor, opencode, etc.)scm— source control operations (GitHub, GitLab, etc.)tracker— issue tracking (GitHub Issues, Linear, etc.)notifier— notifications (Slack, Discord, openclaw, webhook, etc.)workspace— how worktrees are set up (worktree, docker-volume, etc.)
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.
- 9d ago First seen · 334 lines · 4,518 tokens per session scan A 03509e164ea3
agent-orchestrator-ts AGENTS.md is an instructions file published in the GitHub repository jleechanorg/agent-orchestrator-ts (8 stars, last pushed 3d ago), licensed MIT. It adds 4,518 tokens to every session, about $0.0181 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-10-02.
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).
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).
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.
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.