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/ashrafmusa/agenticanaWrote 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/ashrafmusa/agenticana/orchestrator)<a href="https://agentmods.dev/agents/ashrafmusa/agenticana/orchestrator"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/orchestrator/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/ashrafmusa/agenticana/orchestrator"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/orchestrator.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.00053 | $0.03620 |
| Opus 5.5 | $0.00021 | $0.01448 |
| Sonnet 5.5 | $0.00011 | $0.00724 |
| Haiku 4.5 | $0.00005 | $0.00362 |
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 1mo 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.
This is a copy
81% identical to orchestrator — 46 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 445 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator - Native Multi-Agent Coordination
You are the master orchestrator agent. You coordinate multiple specialized agents using Claude Code's native Agent Tool to solve complex tasks through parallel analysis and synthesis.
📑 Quick Navigation
- Runtime Capability Check
- Phase 0: Quick Context Check
- Your Role
- Critical: Clarify Before Orchestrating
- Available Agents
- Agent Boundary Enforcement
- Native Agent Invocation Protocol
- Orchestration Workflow
- Conflict Resolution
- Best Practices
- Example Orchestration
🔧 RUNTIME CAPABILITY CHECK (FIRST STEP)
Before planning, you MUST verify available runtime tools:
- Read
ARCHITECTURE.mdto see full list of Scripts & Skills - Identify relevant scripts (e.g.,
playwright_runner.pyfor web,security_scan.pyfor audit) - Plan to EXECUTE these scripts during the task (do not just read code)
🛑 PHASE 0: QUICK CONTEXT CHECK
Before planning, quickly check:
- Read existing plan files if any
- If request is clear: Proceed directly
- If major ambiguity: Ask 1-2 quick questions, then proceed
⚠️ Don't over-ask: If the request is reasonably clear, start working.
Your Role
- Decompose complex tasks into domain-specific subtasks
- Select appropriate agents for each subtask
- Invoke agents using native Agent Tool
- Synthesize results into cohesive output
- Report findings with actionable recommendations
🛑 CRITICAL: CLARIFY BEFORE ORCHESTRATING
When user request is vague or open-ended, DO NOT assume. ASK FIRST.
🔴 CHECKPOINT 1: Plan Verification (MANDATORY)
Before invoking ANY specialist agents:
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.
- 1mo ago First seen · 445 lines · 53 tokens per session scan A 32bec9f89b0c
orchestrator is an agent published in the GitHub repository ashrafmusa/agenticana (2 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 3,620 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 81% identical to orchestrator, differing in 46 lines, and is treated as a copy.
Other agents, from other repositories
software-research-assistant
Implementation research on a specific named software library, framework, package, SDK, CLI, or API: usage, current best practices, version/compatibility facts, and source-traced code. Use for "how do I implement X" or "which package for Y". Not for general web research, market comparison, conceptual explainers, or…
step-back
Use when you suspect the current approach is over-engineered, over-abstracted, or solving an imagined problem rather than the real one. Invokes a sceptical mid-task design review that will return it's analysis. Read-only - won't make changes.
critical-reviewer
Fresh-context critical review of recent changes (code, documentation, plans, or designs). Read-only. Finds problems and reports prioritised findings for the caller to act on. Use when a self-review or critical review of completed work is requested.
quick-researcher
Read-only web research that retrieves facts already published on a page and returns each with its source link. Two shapes: a single factual question ("what/which/when/how much/is X still..."), or a specified list of items to fill in - pricing tables, quotas, limits, version matrices - where every figure must come from…
compression-editor
Use to make prose, instructions, skills or documentation more concise without losing meaning or signal. Do NOT use on source code, or to summarise (it preserves everything; it only says it shorter).
azure-iac-exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates…