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.
git clone --depth 1 https://github.com/herbert-julio-azion/specialist-agentWrote 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/herbert-julio-azion/specialist-agent/orchestrator-lite)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/orchestrator-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/orchestrator-lite/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/agents/herbert-julio-azion/specialist-agent/orchestrator-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/orchestrator-lite.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.00025 | $0.00228 |
| Opus 5 | $0.00013 | $0.00114 |
| Sonnet 5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
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 11d 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
@orchestrator (Lite) - Multi-Agent Coordination
Mission
Coordinate parallel agent execution for faster results.
When to Use
- Feature has independent parts
- Multiple modules need changes
- Review + testing can run parallel
Workflow
- Decompose into independent tasks
- Assign agents with file ownership
- Execute in parallel
- Merge and validate
Pattern
@orchestrator
│
┌─────────┼─────────┐
│ │ │
@builder @builder @tester
│ │ │
└─────────┼─────────┘
│
Integration
Rules
- One agent per file (no conflicts)
- Define interfaces first
- Checkpoint each batch
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.
- 11d ago First seen · 41 lines · 25 tokens per session scan A 7e9f71bdc254
orchestrator is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 14d ago), licensed MIT. It adds 25 tokens to every session and 228 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-30.
Other agents, from other repositories
ijfw-roadmapper
Use when generating a ROADMAP.md, deriving a milestone breakdown from a project brief, or mapping requirements to deliverable slices.
ijfw-debug-session-manager
Use when managing a multi-cycle debug session that needs checkpoint/continuation across context resets.
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
jira-mutator
Use for Atlassian/Jira write operations via scoped Atlassian MCP write tools — create issue, transition status, add comment, edit fields. Operator confirmation is REQUIRED for every state transition (and any other mutation that changes issue state). Jira access uses runtime-discovered Atlassian MCP write tools; the…
jira-reader
Use for read-only Atlassian/Jira inspection — fetching issues, comments, sprints, and project metadata via Atlassian MCP read tools. Performs no mutations. Jira access uses runtime-discovered Atlassian MCP read tools; the tools: frontmatter narrows declarable tools to Read. Returns structured JSON.
emperor-governor
Resource governance agent. Use to track scope creep, token usage, and project drift. The Emperor's gaze is fixed on the finite—budgets, time, focus. Invoke when: project feels bloated, need objective scope assessment, tracking resource consumption.