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 tddgit 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/tdd)<a href="https://agentmods.dev/skills/jstoup111/ai-conductor/tdd"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/tdd/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/tdd"><img src="https://agentmods.dev/badge/skills/jstoup111/ai-conductor/tdd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 286 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00041 | $0.06312 |
| Opus 5.5 | $0.00016 | $0.02525 |
| Sonnet 5.5 | $0.00008 | $0.01262 |
| Haiku 4.5 | $0.00004 | $0.00631 |
Grade A, and why
tdd 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 22d 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 — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Enforces test-driven development with domain integrity as a first-class concern. Every change goes through a five-step cycle with implementer isolation — the RED agent only sees tests, the GREEN agent only sees source, and the DOMAIN reviewer has veto authority over both.
Host mechanics: Delegate RED, GREEN, and DOMAIN work through the selected host's available subagent facility. Claude Code uses its Agent tool and Claude model labels; other supported hosts use their native equivalents. The host mechanism may differ, but it MUST preserve this cycle's RED → DOMAIN → GREEN → DOMAIN → COMMIT order, scoped verification, review vetoes, and commit gates.
Documentation boundary
Do not start a RED/GREEN cycle for ordinary human-facing documentation, and do not add tests that
assert documentation wording, headings, formatting, placement, links, or repository explanations.
Documentation-only requests are delivered from /explore. Keep tests for machine-consumed documents
only when they assert generated or runtime behavior (for example OpenAPI contracts or generated
repository-harness functionality), never prose shape.
Suite-failure repair
When BUILD returns after test_suite fails, read the engine's retry diagnostics and
referenced .pipeline/test-suite-evidence.json, and include the relevant failure evidence
in RED/GREEN dispatches. Repair and verify the affected tests through
ai-conductor scoped-run <selectors...>, then commit. Leave aggregate re-verification to
test_suite; a scoped PASS does not establish an aggregate PASS.
SHIP verdict artifacts are read-only
During BUILD, .pipeline/prd-audit.json is the typed PRD verdict authority (ADR D2.2), and
.pipeline/prd-audit.md is its derived human report. .pipeline/architecture-review-as-built.md,
.pipeline/architecture-review-as-built.json, .pipeline/prd-audit-code-stamp.json, and
.pipeline/architecture-review-as-built-code-stamp.json are read-only SHIP validator evidence.
Never write, delete, rename, or recreate them. Reading .pipeline/remediation.json and the cited
verdict artifact remains allowed. Use that read-only evidence when the task needs finding detail.
What ships with it
5 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.
- 22d ago Changed · +4 lines a9efd73d1d6a
- 26d ago Changed · +11 lines 670d85eed45e
- 1mo ago Changed · +2 lines 42397c99f02d
- 1mo ago Changed · +10 lines ce8e216bdac4
- 1mo ago Changed · +12 lines e10993fd1c5e
- 2mo ago First seen · 434 lines · 41 tokens per session scan A 02bbf7f954ca
tdd is a skill published in the GitHub repository jstoup111/ai-conductor (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 6,312 once invoked, about $0.0002 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-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.