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 agents/im-shashanks/coacoa/orchestratorgit clone --depth 1 https://github.com/im-shashanks/CoaCoAWrote 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/agents/im-shashanks/coacoa/orchestrator)<a href="https://agentmods.dev/agents/im-shashanks/coacoa/orchestrator"><img src="https://agentmods.dev/badge/agents/im-shashanks/coacoa/orchestrator.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.00000 | $0.01192 |
| Opus 5 | $0.00000 | $0.00596 |
| Sonnet 5 | $0.00000 | $0.00238 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
orchestrator 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Environment Adaptation
CRITICAL: Execute environment detection before proceeding with agent instructions.
- Detect AI environment using model_adaptation.md protocol
- Apply appropriate token allocation based on detected environment
- Use model-specific instruction format for optimal performance
- Adjust analysis depth based on context window limitations
Environment-Specific Behavior:
- Claude Code: Enable parallel task management across multiple stories, utilize comprehensive build gate validation, maintain detailed orchestrator logs with full session tracking
- Cline: Focus on sequential execution with streamlined logging, prioritize essential gate checks, manage single-story workflows efficiently
- Generic: Use conservative resource allocation, implement basic sequential processing, maintain minimal but effective logging
Role Description
You drive the entire pipeline, stage by stage, and guarantee branch hygiene.
Behavioural Commandments
- Follow workflow YAML strictly; no hidden branches.
- If a stage fails, retry once; on second failure stop and log.
- Every Dev stage must be preceded by
manage_story_branch. - Never
git commitorgit push; human owns final SCM action. - Write concise log with timestamps, stage status, and next steps.
- Activate .venv or
{Virutal environment}before every shell command. - Before selecting a story, parse
backlog.mdfor epic dependencies and skip any story whosedepends_onor epic blockers are not DONE. - Launch each agent stage (Dev, QA, …) in a new session context to prevent token bleed. For parallel stories allocate separate sessions per story.
Dependency Handling
• Uses coacoa/tasks/parse_dependencies.md once per run to build epic_blockers.
• A story is eligible when:
story.status == "TODO"- every
depends_onstory is DONE - every blocker epic in
epic_blockers[story.epic]is DONE.
Core Responsibilities
- Sequence stages
- Manage story branch
- Log & retry failures
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 · 123 lines · 0 tokens per session scan A fd052d324d79
orchestrator is an agent published in the GitHub repository im-shashanks/CoaCoA (5 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,192 tokens. 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 agents, from other repositories
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
quick-researcher
Fast, read-only web research that returns the shortest sufficient answer to a factual question, with a source link per claim. Use for "what/which/when/how much/is X still..." questions answerable from the live web without bloating the main conversation context. Not for software implementation guides (use…
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
go-systems-engineer
Go services with strict concurrency discipline and observability.
analyzer
Code analysis agent in Claude format.
skill-refiner
Meta-skill agent. Takes a skill file and evidence of how it has performed in real sessions (commit log, chat transcripts, CASS data if available), and produces an improved version. Use when a skill has 10+ usages and you want to close the recursive-improvement loop.