Borrowing it
Nothing to install: this file belongs to anthony-spruyt/claude-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/anthony-spruyt/claude-plugins/main/.claude/skills/orchestration-retro/SKILL.mdgit clone --depth 1 https://github.com/anthony-spruyt/claude-pluginsWrote 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/anthony-spruyt/claude-plugins/orchestration-retro)<a href="https://agentmods.dev/skills/anthony-spruyt/claude-plugins/orchestration-retro"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/orchestration-retro/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/skills/anthony-spruyt/claude-plugins/orchestration-retro"><img src="https://agentmods.dev/badge/skills/anthony-spruyt/claude-plugins/orchestration-retro.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.00041 | $0.00493 |
| Opus 5.5 | $0.00016 | $0.00197 |
| Sonnet 5.5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
orchestration-retro 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 3d 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
Orchestration Retro
Report to the owner only; never post it to GitHub.
1. Run the report
.claude/skills/orchestration-retro/retro.sh --since "$(date -d '30 days ago' +%F)"
Use another --since date if the owner names a window. The script is read-only and prints helper counts and output tokens per agent type and model, general-purpose helpers that ran on Opus, review verdicts, fix rounds per PR (fix-check reviews), and non-None ### Agent Definition Feedback, with [definition], [rules] and [brief] items counted and listed separately.
2. Read it
- Routing: general-purpose helpers on Opus mean a brief should have named
builder,reviewerorchore-runner, or a rule or agent description is unclear. - Over-delegation: many
chore-runnerruns with a low output-token total (under ~1k per run, total divided by runs in the agent table), or[brief]feedback fromchore-runnersaying the job was trivial, means short jobs are being handed off against theorchestrationskill's Routing section. - Rework: a PR with a fix round means the full review or the builder's self-review missed something; two (at cap) point to a gap in the brief or design.
- Feedback:
[definition]and[rules]entries not yet applied to the agent file,CLAUDE.mdor rules file;[brief]entries repeated across runs point to a gap in theorchestrationskill.
3. Propose changes
Propose up to 5 one-line changes to the orchestration skill or an agent file. They land in repo-operator src/templates/.claude/skills/orchestration/SKILL.md or src/templates/.claude/agents/*.md, not in the repo's synced copy. Tie each to the report line that supports it.
Change nothing until the owner approves.
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.
- 3d ago First seen · 32 lines · 41 tokens per session scan A ae5f4acc9b88
orchestration-retro is a skill published in the GitHub repository anthony-spruyt/claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 493 once invoked, about $0.0002 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-10-16.
Other skills, from other repositories
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…