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-setup/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-setup)<a href="https://agentmods.dev/skills/mrlarson2007/copilot-tdd-harness/tdd-setup"><img src="https://agentmods.dev/badge/skills/mrlarson2007/copilot-tdd-harness/tdd-setup.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.1 | $0.00053 | $0.00999 |
| Opus 5 | $0.00026 | $0.00500 |
| Sonnet 5 | $0.00011 | $0.00200 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
tdd-setup 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 7d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdd-setup
Use this skill when the repository needs project-specific TDD configuration.
Goals
Generate:
.github/instructions/tdd-patterns.instructions.md.github/skills/tdd-red/assets/project-testing-patterns.md.github/skills/tdd-green/assets/project-code-style-patterns.md.github/skills/tdd-refactor/assets/project-refactor-patterns.md
These three phase asset files are canonical placeholders and must always exist, even before final pattern extraction.
Pattern Extraction Step
- Ensure canonical placeholder files exist for RED, GREEN, and REFACTOR style guides.
- Prompt the user to select or specify exemplar test files and production code files that best represent the project's preferred style and conventions.
- Use LLM-powered analysis to extract:
- Test structure, naming, and assertion patterns from the exemplar test files (for RED)
- Code style, idioms, and formatting conventions from the exemplar production files (for GREEN)
- Refactoring and surrounding-code consistency patterns from both (for REFACTOR)
- Summarize the extracted patterns and present them to the user for confirmation or editing.
- After confirmation, update:
.github/skills/tdd-red/assets/project-testing-patterns.md.github/skills/tdd-green/assets/project-code-style-patterns.md.github/skills/tdd-refactor/assets/project-refactor-patterns.md
If the user does not provide example files, run interview-only mode.
Interview Workflow
- Present extracted patterns first, then ask for confirmation or corrections.
- If a value or pattern is missing, ask:
- What test runner do you use?
- What build command should the agent use for validation when a build step is needed?
- Where are your test files?
- What naming convention do you use for test methods or test cases?
- What assertion library do you use?
- What mocking approach or mocking library do you use?
- What testing patterns should RED follow (for example AAA, table-driven, Given-When-Then naming)?
- What implementation/code-style patterns should GREEN follow (for example naming, formatting, guard clauses, error handling conventions)?
- What refactoring style patterns should REFACTOR follow (for example surrounding-code consistency, helper extraction thresholds, readability priorities)?
- Are there project-specific testing patterns for time, logging, HTTP, database, or other dependencies?
What ships with it
4 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.
- 7d ago First seen · 101 lines · 53 tokens per session scan A bd95c328a815
tdd-setup is a skill published in the GitHub repository mrlarson2007/copilot-tdd-harness (5 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 999 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 skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
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.
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…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
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.