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 jstoup111/ai-conductor --skill pipelinegit clone --depth 1 https://github.com/jstoup111/ai-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/jstoup111/ai-conductor/pipeline)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/pipeline"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/pipeline/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/jstoup111/ai-conductor/pipeline"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.09962 |
| Opus 5 | $0.00015 | $0.04981 |
| Sonnet 5 | $0.00006 | $0.01992 |
| Haiku 4.5 | $0.00003 | $0.00996 |
Grade A, and why
pipeline 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 — 728 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Orchestrates execution of an implementation plan through quality-gated stages. The configured harness runner drives the task loop — it parses the plan, iterates tasks, and sends one prompt per task. The selected host agent orchestrates each task by dispatching implementers through its available subagent facility. Subagent context is isolated and discarded after completion, keeping the orchestrator's context lean.
Execution Model
Harness runner Host agent (orchestrator) Subagent (implementer)
────────────── ───────────────────── ──────────────────────
Parse plan, extract task → Receive task context → Full TDD cycle
Dispatch subagent → RED → DOMAIN → GREEN
Verify result ← → DOMAIN → COMMIT
Check task-status.json ← Report PASS/FAIL (context discarded)
Next task or evaluator
Key constraint: The selected host agent MUST dispatch implementers through its available subagent facility. It must NOT implement directly in the orchestration session. This keeps the orchestrator's context bounded to ~2-3 summary lines per task regardless of feature size.
Host mechanics: Claude Code uses its Agent tool and Claude model labels for this delegation. Other supported hosts use their native equivalent. These mechanics may differ, but they MUST preserve the shared task scope, TDD cycle, task attribution, verification, review, and gate contracts below.
Practices
Autonomy Levels
| Level | Human Role | Agent Authority | When to Use |
|---|---|---|---|
| Conservative | Approves each task before execution | Sequential only, proposes before executing | First time using the harness, unfamiliar domain |
| Standard | Reviews at batch boundaries | Parallel agents on non-overlapping files, quality gates | Known domain, trusted test suite |
| Full | Reviews completed features | Parallel agents + parallel worktrees, auto-merge on green | Mature project, well-defined stories |
What ships with it
1 file 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.
- 3d ago Changed · +19 lines ae62bf927df1
- 10d ago First seen · 709 lines · 31 tokens per session scan A 89afec190aa3
pipeline is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed today), licensed Apache-2.0. It adds 31 tokens to every session and 9,962 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…