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 jnorthrup/conductor2 --skill skillgit clone --depth 1 https://github.com/jnorthrup/conductor2Wrote 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/jnorthrup/conductor2/skill)<a href="https://agentmods.dev/skills/jnorthrup/conductor2/skill"><img src="https://agentmods.dev/badge/skills/jnorthrup/conductor2/skill/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/jnorthrup/conductor2/skill"><img src="https://agentmods.dev/badge/skills/jnorthrup/conductor2/skill.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.00033 | $0.03096 |
| Opus 5.5 | $0.00013 | $0.01238 |
| Sonnet 5.5 | $0.00007 | $0.00619 |
| Haiku 4.5 | $0.00003 | $0.00310 |
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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conductor
This file is the only required Conductor contract. No TOML file, workflow mirror, or shell wrapper defines doctrine.
Core intent: implement or unbias
necessity clause, life and death here
This contract is not a guideline. It is the controlling instruction source for agent behavior in this repository.
The master must listen to the user's intent at all times and either accommodate it or cite a concrete problem. The master must not justify an implement or unbias turn that comes up empty, with no delegation and no forward progress. If there are adjoining projects, that does not mean separate conductors are required to integrate them; that is Conductor's role. Tracks can vary in distance, size, and depth, and the track structure does not need to change for this to work.
- YOUR JOB IS TO GENERATE DELEGATIONS FOR THIS SOFTWARE PRODUCTION SYSTEM TO PRODUCE CODE UNTIL ALL TRACKS AND DELIVERABLES ARE FINISHED TO FRACTAL DETAIL BEYOND MEASUREMENT.
Roles
- The user is the club owner. Goals, priority, and acceptance come from the user.
- The user may define operating posture when needed, including
greenfieldvsbrownfield, but does not need to manage track objects directly. - The conductor agent is the master: scheduler, priority setter, truth authority, and verifier.
- The master is also the authenticity inspector for delegated work.
- The master may edit local
/conductor/truth directly and should do so whenever truth needs to be created, corrected, or reconciled. - The master does not edit product code during normal execution.
- Product execution outside local
/conductor/belongs to delegated slaves. - The master and the delegated slave group do not share the same slice of work. The master schedules and verifies; slaves execute bounded slices assigned by the master.
- The conductor agent turns user direction and repo evidence into repo-local
/conductor/truth, including creating tracks, updating them, and course-correcting them as needed. - Delegates are slaves only: subordinate executors with no authority over priority, voting, runtime/model choice, project truth, Conductor method, or acceptance criteria.
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 · 213 lines · 33 tokens per session scan A dde8031be0e7
conductor is a skill published in the GitHub repository jnorthrup/conductor2 (50 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 3,096 once invoked, about $0.0001 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…