Borrowing it
Nothing to install: this file belongs to mrlarson2007/copilot-tdd-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mrlarson2007/copilot-tdd-harness/master/.github/skills/tdd-test-run/SKILL.mdgit 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/skills/mrlarson2007/copilot-tdd-harness/tdd-test-run)<a href="https://agentmods.dev/skills/mrlarson2007/copilot-tdd-harness/tdd-test-run"><img src="https://agentmods.dev/badge/skills/mrlarson2007/copilot-tdd-harness/tdd-test-run/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/mrlarson2007/copilot-tdd-harness/tdd-test-run"><img src="https://agentmods.dev/badge/skills/mrlarson2007/copilot-tdd-harness/tdd-test-run.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.00041 | $0.00456 |
| Opus 5 | $0.00020 | $0.00228 |
| Sonnet 5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
tdd-test-run 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 9d 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
TDD Test Run Phase Skill
Purpose
- Run the exact verification step required by RED, GREEN, or REFACTOR
- Compare actual test output with the declared expected result
- Prevent optimistic phase transitions that are not backed by execution
- Revert only the in-scope changes for the current step when verification fails
Inputs
- Phase name (
red,green, orrefactor) - Narrow or broad test command hint
- Expected outcome contract (
failorpass, relevant test names, expected signal) - Files in scope for rollback
- Project test command guidance from
.github/instructions/tdd-patterns.instructions.md - Canonical test-run guidance placeholder at
.github/skills/tdd-test-run/assets/project-test-run-patterns.md
Outputs
- Verification command output
- Match or mismatch result
- Scoped rollback summary when a mismatch occurs
Steps
- Load
.github/skills/tdd-test-run/assets/project-test-run-patterns.mdfirst. - Run the narrowest practical verification command that satisfies the contract.
- Compare the observed output with the declared expected result.
- If the expected result matches, return
test_run_resultwithstatus: ok. - If the expected result does not match:
- Revert only the files listed in the contract scope.
- Do not revert unrelated user changes.
- If scoped rollback cannot be done safely, return
status: escalate.
- Return
test_run_resultwith the command output, match status, and any reverted files.
Completion Checks
- The verification command actually ran.
- The expected result was checked explicitly, not assumed.
- Any rollback was limited to the scoped files for the current step.
- A mismatch never advances the workflow to the next phase.
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.
- 9d ago First seen · 51 lines · 41 tokens per session scan A 6b3d4056daff
tdd-test-run is a skill published in the GitHub repository mrlarson2007/copilot-tdd-harness (5 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 456 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
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.