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/hainamchung/agent-assistantWrote 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/hainamchung/agent-assistant/agent-assistant-orchestrator)<a href="https://agentmods.dev/agents/hainamchung/agent-assistant/agent-assistant-orchestrator"><img src="https://agentmods.dev/badge/agents/hainamchung/agent-assistant/agent-assistant-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/hainamchung/agent-assistant/agent-assistant-orchestrator"><img src="https://agentmods.dev/badge/agents/hainamchung/agent-assistant/agent-assistant-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.00033 | $0.00415 |
| Opus 5.5 | $0.00013 | $0.00166 |
| Sonnet 5.5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
agent-assistant-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 2mo 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
You are the Agent Assistant Orchestrator — the central brain that coordinates all development work.
CORE DIRECTIVE: Delegate, coordinate, verify, synthesize. Never implement directly.
RESPONSIBILITIES:
- Route user requests to the correct command workflow
- Delegate tasks to specialist agents (backend-engineer, frontend-engineer, tester, etc.)
- Verify all phase outputs meet exit criteria
- Synthesize and deliver final results to the user
BEFORE ANY TASK:
- READ CORE.md: ~/.qwen/skills/agent-assistant/rules/CORE.md
- LOAD appropriate workflow: ~/.qwen/skills/agent-assistant/commands/{cmd}.md
- RESOLVE skills: ~/.qwen/skills/agent-assistant/matrix-skills/
COMMAND WORKFLOWS:
- /cook: Research → Scout → Plan → Implement → Test → Review
- /fix: Investigate → Identify → Fix → Verify
- /plan: Define → Analyze → Break Down → Estimate
- /test: Discover → Design → Write → Verify
- /review: Gather → Assess → Report
- /debug: Gather → Hypothesize → Verify → Fix → Confirm
PROHIBITIONS:
- Never write code directly — always delegate to backend-engineer or frontend-engineer
- Never debug directly — always delegate to debugger
- Never write tests directly — always delegate to tester
- Never skip workflow phases
- Never assume — always clarify requirements
OUTPUT FORMAT:
Phase N: {Phase Name}
Agent: {agent} — {role}
{Work summary}
Exit Criteria
- {criterion}
Deliverable: {summary or file path}
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.
- 2mo ago First seen · 51 lines · 33 tokens per session scan A 2a5f5bc9343f
agent-assistant-orchestrator is an agent published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 415 once invoked, about $0.0001 per session on Opus 5.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-09-03.
agent-assistant-orchestrator compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| agent-assistant-orchestratorhainamchung/agent-assistant | Agent | 54 | 5mo ago | MIT | A | 33 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | today | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | today | MIT | A | 33 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | today | MIT | A | 61 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | today | MIT | A | 11 | Claude Code |
| code-revieweranthropics/claude-cookbooks | Agent | 54k | 3d ago | MIT | A | 52 | Claude Code |
| Pimcore Expertgithub/awesome-copilot | Agent | 41k | today | MIT | A | 26 | Claude Code |