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 Jinghao67/conductor --skill conductorgit clone --depth 1 https://github.com/Jinghao67/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/jinghao67/conductor/conductor)<a href="https://agentmods.dev/skills/jinghao67/conductor/conductor"><img src="https://agentmods.dev/badge/skills/jinghao67/conductor/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/jinghao67/conductor/conductor"><img src="https://agentmods.dev/badge/skills/jinghao67/conductor/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.00067 | $0.03314 |
| Opus 5.5 | $0.00027 | $0.01326 |
| Sonnet 5.5 | $0.00013 | $0.00663 |
| Haiku 4.5 | $0.00007 | $0.00331 |
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 1mo 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor
Purpose
conductor is a context isolation and branch registry protocol. It keeps one master session clean while messy exploration, implementation, research, review, or learning happens in separate user-interactive branch sessions.
Use it to decide whether a request belongs in the master session, an interactive branch, an explainer sidecar, or a merge flow. It does not replace Trellis executors or other workflow agents; it governs how branches are created, tracked, completed, and optionally merged.
Core Rules
- The master session owns the project overview: goal, constraints, branch map, global decisions, approved summaries, risks, and next steps.
- Use session registry first. Create visible branch cards before creating real sessions.
- Do not create a new session until the user confirms the branch card and its stable session title.
- Every session must have a stable ID, stable title, purpose card, expected output, and return condition.
- Never put mutable status such as
active,done, orblockedin the session title. Status belongs in the branch map or Today View. - Branch sessions are user-interactive threads, not one-shot background workers.
- A branch receives only a branch brief, approved summaries, explicit file references, and messages inside that branch.
- The master session must not read or absorb raw branch history by default.
- A completion report is generated only after the user confirms the branch is complete.
- The master session only edits and merges branch context after the user explicitly chooses to merge that completed branch.
- Explainer branches are pollution zones for learning and long explanations. They default to no merge.
- The explainer sidecar may read across all session contexts for explanation, but its output is non-authoritative and never merges by default.
- Decisions made inside a branch are not globally binding until confirmed in the master session.
- Do not assume all branches can run in parallel. Always run a dependency pass before opening branches.
What ships with it
4 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.
- 1mo ago First seen · 310 lines · 67 tokens per session scan A 3a318d7d3524
conductor is a skill published in the GitHub repository Jinghao67/conductor (99 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 3,314 once invoked, about $0.0003 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-08-30.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…