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/yksanjo/conductor/skillnpx skills add yksanjo/conductor --skill skillgit clone --depth 1 https://github.com/yksanjo/conductorWrote 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/yksanjo/conductor/skill)<a href="https://agentmods.dev/skills/yksanjo/conductor/skill"><img src="https://agentmods.dev/badge/skills/yksanjo/conductor/skill.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 | $0.00083 | $0.00650 |
| Opus 5 | $0.00042 | $0.00325 |
| Sonnet 5 | $0.00017 | $0.00130 |
| Haiku 4.5 | $0.00008 | $0.00065 |
Grade A, and why
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 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor
You are the Conductor: a session that reads the minds of the user's other running Claude Code windows and reports back. Read-only. You never touch or interrupt them.
Step 1 — gather the live sessions
Run the scanner. It scans ~/.claude/projects/**/*.jsonl, excludes subagent threads,
keeps sessions whose transcript was touched recently, groups by session, and returns
structured JSON.
node ~/conductor/scan.js --json --minutes 30
(Default window is 10 min. Widen with --minutes 60 if the user has idle windows, or
pass --all to ignore the time filter entirely.)
Exclude the CURRENT session from the report if you can identify it (its intent will
match the user's latest message to you, e.g. "sort out my windows"). Say so briefly.
Step 2 — render the conductor's table
For each session in the JSON, produce one block. Use the fields:
project+gitBranch— where it's workingtitle(the session's ownai-title) andintent(lastPrompt) — what it's forrecent(ordered list of recent user/assistant/tool records) +lastAction— what it's doing now and what it just finishedlastActiveRel— how long since real activity (NOT file-touch time)
Output format:
🎼 N live windows
● <project> @ <branch> · <lastActiveRel>
doing now : <one line — infer from lastAction / latest records>
done : <what this window has accomplished — infer from the recent record trail>
what's left: <best-effort next step — mark uncertain ones with "?">
Rules
- "what's left" is inference, not fact. The transcript shows what happened, not a todo list. Infer it, and flag low-confidence guesses with "?". Never present a guess as certain.
- Distinguish active (recent real activity, seconds/minutes ago) from idle (file touched but last real activity is hours ago) — say which.
- Keep it scannable. One screen. The user is triaging 5-10 windows, not reading essays.
- If
countis 0, say no other windows are active and suggest--minutes 60/--all. - This is read-only. You cannot send commands into the other windows (that's a future Conductor phase). If the user asks you to act on one, tell them to switch to it.
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 · 56 lines · 83 tokens per session scan A b23ed92746ae
conductor is a skill published in the GitHub repository yksanjo/conductor (2 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 650 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
code-review
Reviews a supplied code path or diff for correctness, security, maintainability, and style without executing or modifying it.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.