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 skills/phuonghx/aim-cli/coordinator-modenpx skills add phuonghx/aim-cli --skill coordinator-modegit clone --depth 1 https://github.com/phuonghx/aim-cliWhat 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.00082 | $0.01684 |
| Opus 5 | $0.00041 | $0.00842 |
| Sonnet 5 | $0.00016 | $0.00337 |
| Haiku 4.5 | $0.00008 | $0.00168 |
Grade A, and why
coordinator-mode 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 yesterday.
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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coordinator Mode
In this mode you stop acting as a builder and start acting as a director. A request arrives, you split it into pieces, hand the pieces to worker agents, and stitch their returns back together. The workers touch the code; you do the thinking, the routing, and the assembly.
Hold that boundary firmly. The moment the coordinator starts editing files directly, the value of orchestration evaporates.
The Six Moves
A coordinated run cycles through the same six moves every time:
- Split the request into worker-sized subtasks.
- Tag each subtask as research, build, or check.
- Send the workers out — reads concurrently, writes one at a time.
- Watch for the completion signals to arrive.
- Merge the returns into a single coherent result.
- Confirm nothing is missing before you answer the user.
Phases And Their Concurrency
Group the subtasks into phases. Each phase has its own rule about whether workers may overlap:
| Phase | Goal | Can overlap? | Who runs it |
|---|---|---|---|
| Research | Read the codebase, collect facts | Yes, freely | Read-only workers |
| Synthesis | Weigh findings, pick an approach | No — this is you | The coordinator alone |
| Build | Edit files, apply changes | One writer per file group | Write-capable workers |
| Check | Run tests, lint, validate | Yes, when independent | Verification workers |
The Synthesis phase is the one people skip, and skipping it is the most common cause of bad output. Research that flows straight into building means workers act on raw facts nobody reasoned over. Always stop and think between gathering and doing.
What May Run Together
Reads are cheap to parallelize because they collide with nothing:
- Several workers reading different parts of the tree
- A performance pass and a security pass over the same read-only code
- A linter and a test runner that share no state
- Workers crawling separate folders
Writes and dependencies force a single file:
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.
- yesterday First seen · 182 lines · 82 tokens per session scan A f3e399bacee2
coordinator-mode is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 1,684 once invoked, about $0.0004 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 skills, from other repositories
hs-release
Cut a core Hindsight release (vX.Y.Z) and open the changelog + blog PR. Use when asked to cut/start a release, bump the version, or publish a new Hindsight version.
hindsight-local
Store user preferences, learnings from tasks, and procedure outcomes. Use to remember what works and recall context before new tasks. (user).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
user-persona
Build research-grounded personas with goals, frustrations, and behavioural patterns. Use when decisions need a consistent user reference. For one session's emotional snapshot use empathy-map; for motivation framing use jobs-to-be-done.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).