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-refactor/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-refactor)<a href="https://agentmods.dev/skills/mrlarson2007/copilot-tdd-harness/tdd-refactor"><img src="https://agentmods.dev/badge/skills/mrlarson2007/copilot-tdd-harness/tdd-refactor.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.00031 | $0.00385 |
| Opus 5 | $0.00015 | $0.00192 |
| Sonnet 5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
tdd-refactor 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.
What it actually says
TDD Refactor Phase Skill
Purpose
- Improve code and test design after green
- Preserve all existing behavior
- Prioritize readability over forced deduplication
- Introduce helpers/builders when they improve future test authoring
Inputs
- Commit details from commit stage (sha/message)
- Committed baseline
- Readability goals
- Project refactor patterns from
.github/instructions/tdd-patterns.instructions.md - Canonical REFACTOR style guide placeholder at
.github/skills/tdd-refactor/assets/project-refactor-patterns.md
Outputs
- Refactor diff
- Test pass evidence
- Helper/builder notes
Steps
- Load
.github/skills/tdd-refactor/assets/project-refactor-patterns.mdfirst, then load core asset files for refactor patterns, anti-patterns, and test readability - Inspect surrounding code around each in-scope change before refactoring
- Refactor code and tests as needed
- Use
tdd-test-runwith atest_run_requestcontract whose expected result is a passing validation for the touched slice, then the broader suite required by project policy - If the observed result does not match the expected REFACTOR outcome, revert only the scoped refactor changes and return to the pre-refactor baseline
- Return contract output
Completion Checks
- All behavior preserved
- Code and tests are more readable/maintainable
- Helpers/builders introduced only when justified
What ships with it
2 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 · 47 lines · 31 tokens per session scan A 5635a42e07bc
tdd-refactor is a skill published in the GitHub repository mrlarson2007/copilot-tdd-harness (5 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 385 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.
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.