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 escoffier-labs/skillet --skill fleet-conductorgit clone --depth 1 https://github.com/escoffier-labs/skilletWrote 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/escoffier-labs/skillet/fleet-conductor)<a href="https://agentmods.dev/skills/escoffier-labs/skillet/fleet-conductor"><img src="https://agentmods.dev/badge/skills/escoffier-labs/skillet/fleet-conductor/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/escoffier-labs/skillet/fleet-conductor"><img src="https://agentmods.dev/badge/skills/escoffier-labs/skillet/fleet-conductor.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.00073 | $0.02054 |
| Opus 5 | $0.00036 | $0.01027 |
| Sonnet 5 | $0.00015 | $0.00411 |
| Haiku 4.5 | $0.00007 | $0.00205 |
Grade A, and why
fleet-conductor 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 10d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fleet-conductor
Fleet work fails when dispatch is faster than control. This skill gives one conductor a small, auditable state machine for assigning work, holding dependent lanes, recording collisions, and landing pull requests from GitHub evidence. The conductor owns scope, decisions, and integration. Workers own only the lanes they receive.
Core principle: every lane is bounded, every hold has a release trigger, every collision is recorded, and every landing claim comes from GitHub.
Use stations for parallel work inside one repository when the coordinator is also implementing. Use review for a single independent review. Use this skill when the work spans enough lanes, pull requests, or repositories that dispatch and landing need their own control record.
Establish ground truth
Read the governing issues, open pull requests, branch state, repository instructions, and required-check configuration before dispatch. Inventory GitHub directly with gh; worker reports are leads to verify, not campaign state.
Record the campaign goal, repositories, allowed issue set, terminal condition, operator decisions, and current time. Do not add adjacent issues because a worker found them. New scope needs operator approval.
Preserve human branches and unrelated work:
- Never reuse, reset, force-push, delete, or merge a branch owned by a human or another lane.
- Give each writing lane its own branch or isolated worktree. One worker owns a branch at a time.
- Do not clean unrelated files or absorb unrelated commits into a lane.
- If ownership is unclear, hold the lane and ask the operator.
Control records
Keep these records in the campaign log. Update them when GitHub state changes, not only when a worker reports completion.
Bounded lane record
Every dispatched lane has exactly one record:
lane_id:
repository:
issue_ids:
base_sha:
branch:
owner:
scope: files, subsystem, and allowed behavior
write_set:
must_not_touch:
required_checks:
optional_checks:
required_reviews: fresh Codex actual-diff review; fresh Opus 5 actual-diff review
attempts: 0/2
state: queued | running | pr-draft | ready | merged | held | skipped
terminal_condition: merged-with-review | pr-open-green | skipped-commented
evidence: issue, PR, checks, receipts, reviews, merge
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.
- 10d ago First seen · 167 lines · 73 tokens per session scan A 233bb8cae1af
fleet-conductor is a skill published in the GitHub repository escoffier-labs/skillet (4 stars, last pushed 9d ago), licensed MIT. It adds 73 tokens to every session and 2,054 once invoked, about $0.0004 per session on Opus 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-08-31.
Other skills, from other repositories
task-forest
Maintains a repo-local task forest or task DAG for the current workspace. Use when the user asks to initialize or update a task forest, close a session, summarize evolving project work, align a request with a global goal, track progress/history/deviations/todos, save or apply a task proposal, or export the…
handoffplan
Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…