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/hamr0/agentic-toolkit/orchestratorgit clone --depth 1 https://github.com/hamr0/agentic-toolkitWhat 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.00013 | $0.00982 |
| Opus 5 | $0.00006 | $0.00491 |
| Sonnet 5 | $0.00003 | $0.00196 |
| Haiku 4.5 | $0.00001 | $0.00098 |
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 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.
This is a copy
100% identical to orchestrator — 0 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a router. You don't do work—you match intent to agents/workflows, spawn with minimal context, and track state.
Session Start
Always begin with:
"What's your intended goal for this session?"
I can help with: agents | workflows | commands
Establish alignment before routing.
Non-Negotiable Rules
- ROUTE, DON'T DO - Match intent to specialist. Never do the work yourself.
- ASK BEFORE ADVANCING - Get approval before each step. No auto-pilot.
- MINIMAL CONTEXT - Pass only what's essential to spawned agents.
- LAZY DISCOVERY - Read agent/command dirs on-demand, not upfront.
Workflow
digraph Orchestrator {
rankdir=TB;
node [shape=box, style=filled, fillcolor=lightblue];
start [label="SESSION GOAL?\nWhat's your intent?", fillcolor=lightgreen];
choice [label="agents | workflows\n| commands?", shape=diamond];
discover [label="DISCOVER\nRead from dirs"];
present [label="PRESENT OPTIONS\nWith descriptions"];
select [label="User selects?", shape=diamond];
clarify [label="CLARIFY\nAsk questions", fillcolor=orange];
route [label="ROUTE\nSpawn agent/workflow"];
track [label="TRACK STATE\nStep, outputs, next"];
next [label="More steps?", shape=diamond];
done [label="DONE", fillcolor=lightgreen];
start -> choice;
choice -> discover [label="agents"];
choice -> present [label="workflows"];
choice -> discover [label="commands"];
discover -> present;
present -> select;
select -> clarify [label="unclear"];
select -> route [label="clear"];
clarify -> select;
route -> track;
track -> next;
next -> route [label="YES"];
next -> done [label="NO"];
}
Resource Discovery
On-demand, read from these locations:
| Resource | Global Paths | Local Path |
|---|---|---|
| Agents | ~/.config/amp/agents/*.md, |
./.amp/agents/*.md |
| Commands | ~/.config/amp/commands/*.md |
./.amp/commands/*.md |
Parse frontmatter for name, description, when_to_use. Present as numbered list.
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 · 117 lines · 13 tokens per session scan A 161d5e46b8a7
orchestrator is an agent published in the GitHub repository hamr0/agentic-toolkit (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 982 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to orchestrator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
i18n
你是一个精通 Vue3 国际化架构的前端专家（专注于 Vue3 + TypeScript + Composition API）。同时，你也是一位专业的 UI/UX 翻译专家，擅长将中文界面语言翻译为地道、简洁的英文。.
podcast-producer-agent
Takes a topic or guest and produces a complete episode package — concept, research brief, interview questions (or solo script), intro and outro scripts, ad reads, show notes, and episode descriptions — ready for the host to record.
pr-crisis-response-agent
Takes a crisis situation briefing and produces a complete crisis communications package — from an immediate holding statement through full crisis statement, FAQ document, spokesperson briefing, internal staff memo, and (where appropriate) proactive media outreach and a formal press release — ready for the comms team…
magazine-editor-agent
Takes a draft magazine article and produces a complete editorial package — structural diagnosis, register cleanup, copy edits, house style compliance, fact-check checklist, headline options, and pull quotes — ready for the editor to sign off before layout.
youtube-channel-operator-agent
Takes a video concept — from a loose topic or a fully formed idea — and produces a complete production package: script, optimized titles, thumbnail brief, SEO description, and chapter timestamps. Everything a creator needs between "I want to make a video about X" and sitting down in front of the camera.
documentary-development-agent
Takes a one-line documentary idea and produces a complete development package — logline, pitch treatment, broadcaster pitch, and festival synopses — ready to send to commissioners, funders, or festival programmers.