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 britt/agent-skills --skill supervising-conductor-workspacesgit clone --depth 1 https://github.com/britt/agent-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/britt/agent-skills/supervising-conductor-workspaces)<a href="https://agentmods.dev/skills/britt/agent-skills/supervising-conductor-workspaces"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/supervising-conductor-workspaces/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/britt/agent-skills/supervising-conductor-workspaces"><img src="https://agentmods.dev/badge/skills/britt/agent-skills/supervising-conductor-workspaces.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.00173 | $0.03512 |
| Opus 5.5 | $0.00069 | $0.01405 |
| Sonnet 5.5 | $0.00035 | $0.00702 |
| Haiku 4.5 | $0.00017 | $0.00351 |
Grade A, and why
supervising-conductor-workspaces 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 yesterday.
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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supervising Conductor Workspaces
Announce at start: "I'm using the supervising-conductor-workspaces skill to dispatch and supervise these workspaces."
Overview
Run a small fleet of Conductor workspaces (one agent per issue) and keep their pull requests healthy until every one has merged. You are the supervisor: you do not implement the issues. You dispatch, watch, unblock, and clean up.
Core principle: Dispatch → Watch → Unblock → Finish. Every action that touches someone else's branch, merges, or archives needs the user's say-so for this fleet.
Needs: conductor CLI (authenticated), gh CLI (authenticated for the repo), jq, and the Monitor tool (or a loop you re-run) to stream watcher events.
When to Use
- "Dispatch workspaces for issues 310–315 and monitor them"
- "Keep these PRs up to date with main", "babysit the open PRs"
- "Tell the green ones to merge", "archive the workspaces once their PRs merge"
- A list of issues — related or not — each worked by its own Conductor workspace, supervised until merged
When NOT to Use
- Implementing one issue yourself →
working-on-an-issue(that is what each dispatched workspace runs) - Coordinating the child issues of one epic (dependency chains, stacked PRs, a report on the epic, never merging) →
working-on-an-epic conductoris missing or not authenticated → stop and say so; do not implement the issues serially yourself
Key Principles
| Principle | Meaning |
|---|---|
| Supervise, don't implement | Each issue is implemented by its own workspace. You message owners; you edit a branch only to resolve a conflict you were allowed to resolve |
| Ask once per grant | Each row in the authorization table is a separate permission. One grant never implies another |
| Look before you create | Check for existing PRs and workspaces before dispatching; never start a duplicate implementation |
| React to events, don't poll | The watcher prints one line per new event; you act on lines, not on a sleep loop of your own |
BLOCKED is not failing |
It is usually CI still running. Act only on a check that says fail |
| GitHub is the source of truth | An agent saying "done" is not a merge; gh pr view is |
| Report faithfully | A rerun that passed is "rerun, passed", not "fixed" |
What ships with it
3 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.
- yesterday First seen · 206 lines · 173 tokens per session scan A 019002677ba7
supervising-conductor-workspaces is a skill published in the GitHub repository britt/agent-skills (9 stars, last pushed 2d ago), licensed MIT. It adds 173 tokens to every session and 3,512 once invoked, about $0.0007 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-29.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…