Borrowing it
Nothing to install: this file belongs to geserdugarov/agent-orchestrator. 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/geserdugarov/agent-orchestrator/main/AGENTS.mdgit clone --depth 1 https://github.com/geserdugarov/agent-orchestratorWrote 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/geserdugarov/agent-orchestrator/agents-md)<a href="https://agentmods.dev/instructions/geserdugarov/agent-orchestrator/agents-md"><img src="https://agentmods.dev/badge/instructions/geserdugarov/agent-orchestrator/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.1 | $0.01524 | $0.01524 |
| Opus 5 | $0.00762 | $0.00762 |
| Sonnet 5 | $0.00305 | $0.00305 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade B, and why
agent-orchestrator AGENTS.md scanned grade B with 1 finding 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 7d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
Postgres volume — runtime state, not source. **Never traverse, read, modify, permission-repair, delete, or re-run any command against it with elevated privileges.** If a tool reports it as unreadable, that is expected: t How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guide for AI agents
This file is the entry point for AI coding agents (Codex, Claude, etc.) working on this repository. CLAUDE.md is a
symlink to this file, so both conventions resolve to the same content.
It is loaded into every agent session — keep it short. It routes to the authoritative documents; detail belongs there, not here. Update this file only when repository-wide agent instructions, safety rules, or documentation routing change — never to track a moved handler, helper, module, or test.
What this project is
agent-orchestrator is a GitHub-Issue-driven workflow that watches issues on configured repos, drives them through a
label-based state machine, and spawns local CLI agents (codex, claude) in per-issue git worktrees to implement
them and open PRs. State lives entirely in GitHub (one workflow label + one pinned JSON comment per issue), so the
orchestrator process is stateless.
Where the details live
docs/README.md is the documentation landing page: it maps every page in the set, names the focused
page under each area, and explains which addresses stay stable. Open it when the area below is not obviously the right
one.
- User-facing overview:
README.md - Architecture, module ownership, process / agent / push model:
docs/architecture.md, with the per-package inventory on the pages underdocs/architecture/ - Workflow state machine (labels, per-tick flow, pinned state, stage handlers):
docs/state-machine.md, with the label, delivery-stage, conversation-stage, and lifecycle pages underdocs/state-machine/ - Agent roles, conversation contracts, command specs, session lifecycles:
docs/workflow.md, with the role, conversation, and spec pages underdocs/workflow/ - Configuration / env vars:
docs/configuration.mdis the reference, with the observability settings and the operator runbooks underdocs/configuration/; basic knobs in.env.example, common advanced overrides in.env.example.advanced - Observability:
docs/observability.mdmaps every surface, with the event-stream, trajectory, database, dashboard, and usage-parser pages underdocs/observability/ - Security checklist and operator-owned controls:
docs/security.md - Development conventions and the pre-push checklist:
.agents/skills/develop/SKILL.md
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.
- 7d ago First seen · 98 lines · 1,524 tokens per session scan B 0ca7f58f465c
agent-orchestrator AGENTS.md is an instructions file published in the GitHub repository geserdugarov/agent-orchestrator (10 stars, last pushed 8d ago), licensed Apache-2.0. It adds 1,524 tokens to every session, about $0.0076 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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.
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.
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).
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.