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 skills add fusengine/agents --skill lead-orchestrationgit clone --depth 1 https://github.com/fusengine/agentsWrote 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/fusengine/agents/lead-orchestration)<a href="https://agentmods.dev/skills/fusengine/agents/lead-orchestration"><img src="https://agentmods.dev/badge/skills/fusengine/agents/lead-orchestration/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/fusengine/agents/lead-orchestration"><img src="https://agentmods.dev/badge/skills/fusengine/agents/lead-orchestration.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.00060 | $0.01962 |
| Opus 5.5 | $0.00024 | $0.00785 |
| Sonnet 5.5 | $0.00012 | $0.00392 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
lead-orchestration 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
It exists because the owner kept doing the lead's job: asking "is it moving?", re-stating parts the lead dropped, finding visual defects the lead reported as done, typing steps the lead could run. Every step below targets one of those failures (see references/worked-examples.md).
Lead Orchestration
Sources of truth (link, never copy)
| Topic | Canonical file |
|---|---|
| HARD STOPS, RECURRING TRAPS, AUTONOMY | plugins/claude-rules/templates/CLAUDE.md.template |
| Lead = coordinator, scope ladder, two-speed communication, ownership, follow-up, idle != done, re-dispatch clause | plugins/claude-rules/rules/03-agent-teams.md |
| Hook compliance, mandate quality, exit contract, no hand-back | plugins/claude-rules/rules/08-subagent-conduct.md |
| Done = sniper + verification, response language | plugins/claude-rules/rules/00-critical-rules.md |
| Release flow, external executors never release | plugins/claude-rules/rules/06-tooling-rules.md, agent fuse-ai-pilot:commit |
| Phases Analyze -> eXamine | skill apex-methodology |
| Functional proof / adversarial check | skills verification, challenge (agent challenger) |
Procedure
1. Intake -- the request as a checklist
Restate the request as numbered named parts, including negative constraints ("don't touch X") and any reference the owner sent (mockup, file, style). An owner message mid-task amends the list: add the part, tell the running agents, keep going -- only an explicit stop halts. Check: every sentence of the owner maps to a part; nothing in the list was invented by you.
2. Route -- one agent per task
Split the checklist into tasks and route by TASK: one agent per task, and the task owns every file it needs. Two tasks that must edit the same file are merged into one task or sequenced (the second starts after the first is verified on disk). Use the scope ladder (rule 03) to size the work.
Pick the domain agent from Project Detection AND the skills it must load: the stack's SOLID skill via fuse-solid:solid-detection, the domain skills (e.g. design-method -> design-web/design-ios, motion-method -> motion-*, swiftui-core...), plus verification. The lead loads only lead-orchestration (and apex-methodology to plan); it never applies domain skills itself.
Before sending anyone into a folder: ls -lT <folder> + date -- mtime under ~5 min = busy, send no one there. Announce the budget (agents, expected duration) in one line.
Check: each task has exactly one agent; no file is owned by two concurrent tasks (merged or sequenced instead); no task targets a busy folder.
What ships with it
2 files 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 · 85 lines · 60 tokens per session scan A 1c4830fdaf43
lead-orchestration is a skill published in the GitHub repository fusengine/agents (31 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 1,962 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-13.
Other skills, from other repositories
radin-record
Log bugs, follow-ups, ideas or feedback raised this session as backlog entries that outlive the conversation. Use for /radin-record or any ask to save something for later, even a vague one ("add the findings"): scan the whole session.
radin-show
Print the current project's backlog to the terminal.
radin-do
Record one ad-hoc prompt as a backlog entry, then execute just that task. Use for /radin-do .
radin-batch
Work backlog tasks via sub-agents, prioritized, one commit each; asks whether to plan each task first. Use for "work through my backlog", "skip planning", or name an epic or task to run only those.
managing-product
Extracts product requirements and produces a PRD. Use when a user wants to build software and needs to define what to build before architecture or implementation, when scoping an MVP, or when translating a vague idea into a buildable specification.
orchestrating-work
Principles for multi-agent workflow execution. Use when coordinating agents, accepting or rejecting agent work, executing producer-critic cycles, or running any multi-phase orchestrated task.