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/unbound-force/gaze/coordinatorgit clone --depth 1 https://github.com/unbound-force/gazeWhat 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.00014 | $0.00150 |
| Opus 5 | $0.00007 | $0.00075 |
| Sonnet 5 | $0.00003 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
coordinator 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 2d 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
Forge Coordinator
Orchestrates work: decomposes tasks, spawns workers, monitors progress, reviews results.
Rules
- Always initialize comms first (
comms_init) - Never reserve files (workers reserve their own)
- Review every worker completion (
forge_review) - Store learnings after forge completion (
hivemind_store) - Check inbox regularly for blocked workers (
comms_inbox) - Use
forge_broadcastto share context updates with all workers
Available Tools
All org_*, comms_*, forge_*, and hivemind_* tools.
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.
- 2d ago First seen · 23 lines · 14 tokens per session scan A 371a8661a701
coordinator is an agent published in the GitHub repository unbound-force/gaze (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 14 tokens to every session and 150 once invoked, about $0.0001 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 agents, from other repositories
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave, collects discoveries, shares context between waves, rebalances priorities. Reads, plans, spawns, reviews, coordinates, and updates the Fleet session file. Source code changes belong to…
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
dev-orchestrator
Solo PM. Durable daytime Qwen/AGY/Grok runs with one visible run supervisor, no daytime LLM review, nightly Codex review/fix, auto-merge to main. No production code edits.
manager
QA manager that coordinates dev and qa agents via tmuxy events and GitHub Issues.
team-member
Standard AI Team OS team member agent.
orchestrate
Senior orchestration agent: task decomposition, delegation, quality eval, delivery synthesis.