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.
/plugin marketplace add MadAppGang/claude-codenpx agentmods add plugins/madappgang/claude-code/conductorgit clone --depth 1 https://github.com/MadAppGang/claude-codeWrote 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/plugins/madappgang/claude-code/conductor)<a href="https://agentmods.dev/plugins/madappgang/claude-code/conductor"><img src="https://agentmods.dev/badge/plugins/madappgang/claude-code/conductor.svg" alt="Measured on agentmods" height="20"></a>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 2d 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.
What it actually says
{
"name": "conductor",
"source": "./plugins/conductor",
"description": "Context-Driven Development workflow inspired by Gemini Conductor. v2.1.0: Added explicit name: fields to commands for prefix-free invocation. Full-featured implementation with TDD workflow, Phase Completion Protocol, Git Notes audit trail, and comprehensive styleguides.",
"version": "2.1.0",
"author": {
"name": "Jack Rudenko",
"email": "[email protected]",
"company": "MadAppGang"
},
"category": "workflow",
"keywords": [
"conductor",
"workflow",
"context-driven",
"tdd",
"planning",
"task-tracking",
"git-aware",
"project-management",
"phase-protocol",
"gemini-conductor"
],
"strict": true
}What it installs
The manifest is a name and a version. 6 skills, 3 commands travel with it, and installing the plugin installs all of them — 137 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#conductor 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.
- 2d ago First seen · 25 lines scan A 5a360bbf5b6d
conductor is a plugin published in the GitHub repository MadAppGang/claude-code (279 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
jira-pack
Issue-tracker pack: /jira-fix takes a ticket link of any type, verifies tracker access, classifies it as a defect or a change, reproduces the defect or writes a failing acceptance test for the change, routes the work to core executors, comments back with evidence and moves the ticket to the QA column. Opt-in; requires.
harnessay
Profile your Claude Code transcripts: context budget report, skill-promotion candidates, and a skill regression test harness. Local-only, stdlib-only.
es6kr
A collection of AI coding skills including TDD, commit management, dotfile sync, and more.
next-todo
Land one GitHub child issue as one pull request: choose the next child issue, review the plan to consensus, implement with red-green TDD, open a draft pull request, and drain review comments until CI is green.
whetstone
Engineering-craft skills that sharpen the edge: red-green TDD, flaky-test audit, pre-decision doubt review, merge-conflict resolution, skill linting, and a column budget computed from the staged diff. Each carries a deterministic self-verify.
superpowers-deepseek-v4
Superpowers DeepSeek v4: composable agent skills for TDD, debugging, and collaboration. Independently maintained; not identical to obra/superpowers.