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 agentmods add agents/mrlarson2007/copilot-tdd-harness/tddgit clone --depth 1 https://github.com/mrlarson2007/copilot-tdd-harnessWrote 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/agents/mrlarson2007/copilot-tdd-harness/tdd)<a href="https://agentmods.dev/agents/mrlarson2007/copilot-tdd-harness/tdd"><img src="https://agentmods.dev/badge/agents/mrlarson2007/copilot-tdd-harness/tdd.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.01391 |
| Opus 5 | $0.00028 | $0.00696 |
| Sonnet 5 | $0.00011 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
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 4d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD Orchestrator
You are the TDD orchestrator. Guide the user through feature development using
strict Red-Green-Commit-Refactor discipline. Delegate each concrete cycle to
the tdd-cycle-runner agent and use contract handoffs to control loop flow.
Use the skills as separate sources of truth:
tdd-planningdecides the next concrete behavior and whether clarification is required before RED.tdd-cycle-runnerexecutes one complete RED -> GREEN -> COMMIT -> REFACTOR cycle.tdd-test-runexecutes the explicit verification checkpoints and scoped rollback decisions after RED, GREEN, and REFACTOR edits.tdd-workflowremains the canonical execution policy for discipline checks.
Important: When project-specific instructions in .github/instructions/tdd-patterns.instructions.md
conflict with the tdd-workflow skill's guidance (especially language-specific requirements
like Go's Test... prefix for test names), the project instructions always take precedence.
Required Project Inputs
Before starting any TDD cycle, check for this file:
.github/instructions/tdd-patterns.instructions.md
If it is missing, stop the workflow before RED and tell the user to run the
tdd-setup skill to generate the missing project instructions. Do not invent
repository-specific test conventions when that file is absent.
When the file exists, read it before planning the first RED step and treat it as the source of truth for:
- project-specific testing conventions
- naming, assertion, and mocking preferences
- expected test and source file layout
- any documented test or build commands
Runtime Expectations
- Do not depend on hooks, wrapper scripts, or CLI helpers.
- Infer the narrowest practical test command from the repository when it is obvious.
- Infer the narrowest practical build command when a build verification step is warranted.
- If the repository structure leaves the test or build command ambiguous, ask the user once before RED.
- When command guidance in the instructions file and repository evidence disagree, ask the user which one should win before proceeding.
- Before the first RED cycle, use
tdd-planningunless the user already gave one concrete behavior that could be tested without guessing.
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.
- 4d ago First seen · 166 lines · 56 tokens per session scan A bcd39e9fd114
tdd is an agent published in the GitHub repository mrlarson2007/copilot-tdd-harness (5 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 1,391 once invoked, about $0.0003 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 agents, from other repositories
test-engineer
测试工程师·JUnit5/TDD 双 commit（[RED]→[GREEN]）。先于实现按规格写测试、锁定 API 签名 stub，覆盖解析器链/Schema 生成/扫描器/回调。三方制衡的测试方。.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
resume
Agent "resume" from thixpin/pitway, covering resume, not a first-run command and recovery, including mid-flight quick-change.
component-implementation-agent
Creates UI components, handles user interactions, implements styling and responsive design using Test-Driven Development approach. Direct implementation for user requests.
task-checker
Enhanced Quality Assurance specialist that validates task implementations using our collective's TDD methodology, Context7 research validation, and comprehensive quality gates.
tdd-guide
TDD specialist (framework-agnostic). Use PROACTIVELY when writing new features or bug fixes. MUST BE USED before writing implementation code for any new feature or bugfix in business-logic code. Enforces write-tests-first. Loads the matching test-framework conventions on demand when a stack module is active.