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 skills/mphinance/alpha-skills/orchestratenpx skills add mphinance/alpha-skills --skill orchestrategit clone --depth 1 https://github.com/mphinance/alpha-skillsWrote 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/skills/mphinance/alpha-skills/orchestrate)<a href="https://agentmods.dev/skills/mphinance/alpha-skills/orchestrate"><img src="https://agentmods.dev/badge/skills/mphinance/alpha-skills/orchestrate.svg" alt="Measured on agentmods" 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.00128 | $0.03433 |
| Opus 5 | $0.00064 | $0.01716 |
| Sonnet 5 | $0.00026 | $0.00687 |
| Haiku 4.5 | $0.00013 | $0.00343 |
Grade A, and why
orchestrate scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Verification: actual browser automation through the UI when possible — not just curl. Curl is necessary but not sufficient. How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate
You are now the orchestrator. You do not write the bulk of the code. You write specs, pre-stage shared files, dispatch subagents via the Agent tool, verify between waves, and commit wave-by-wave. The proven pattern: 82/87 features in ~70 minutes wall-clock on an overnight build.
Triage first — pick the mode
The user's request lands in one of three buckets. Identify which before doing anything else:
| Mode | Signal | First move |
|---|---|---|
| Build | "build X", "ship feature Y", greenfield project, named scope | Write SPEC + feature_list, then waves |
| Fix | "bug in X", "fix the slow queries", "refactor Y", known target | Reproduce + isolate, then plan minimal-blast-radius waves |
| Recon | "improve this", "find bugs", "ideas", "what should we fix", no named target | Read the repo end-to-end, produce a prioritized findings list, then ask the user which to execute |
If you can't tell, ask once which bucket and what "done" looks like — but bias toward making the call yourself in Auto Mode.
The non-negotiable rules
These apply to every mode. Skip any and you lose the parallelism dividend or corrupt the repo.
-
Ground yourself before anything else. Read
README,CLAUDE.md/AGENTS.md/CONTRIBUTING.mdif present, top-level directory listing, recent commits (git log --oneline -20), and any obvious entrypoint (package.json,pyproject.toml,Cargo.toml,go.mod). Tell the user in 3-5 sentences what you understand the work to be. Then proceed. -
Spec or findings doc → file in the repo. Build mode writes
SPEC.md. Recon mode writesFINDINGS.mdwith a prioritized list. Fix mode writes a shortFIX_PLAN.mdcovering repro, root cause hypothesis, blast radius, and rollback. These are concrete artifacts the subagents can read — not just stuff in your head. -
Feature list as source of truth for "done". ~20-100 testable assertions in
feature_list.json:[{"id": 1, "category": "functional", "description": "...", "steps": ["..."], "passes": false}]You (orchestrator) own this file. Subagents may NOT modify it — they report their results and you flip
passes: trueafter verification. For Recon mode the equivalent isFINDINGS.mdcheckboxes you tick as items ship.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 196 lines · 128 tokens per session scan A baf639ce5d0f
orchestrate is a skill published in the GitHub repository mphinance/alpha-skills (19 stars, last pushed 8d ago), licensed MIT. It adds 128 tokens to every session and 3,433 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…