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-commit/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-commit)<a href="https://agentmods.dev/skills/mrlarson2007/copilot-tdd-harness/tdd-commit"><img src="https://agentmods.dev/badge/skills/mrlarson2007/copilot-tdd-harness/tdd-commit/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-commit"><img src="https://agentmods.dev/badge/skills/mrlarson2007/copilot-tdd-harness/tdd-commit.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.00036 | $0.00220 |
| Opus 5.5 | $0.00014 | $0.00088 |
| Sonnet 5.5 | $0.00007 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
tdd-commit 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 1mo 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 Commit Phase Skill
Purpose
- Create an atomic commit for the green state
- Enforce one-commit-per-green discipline
- Require clear, descriptive commit messages
- No refactor or new behavior in this phase
Inputs
- Green status
- Commit scope and message template
- Skill and asset references
Outputs
- Commit sha
- Files committed
- Commit message
Steps
- Load asset files for commit discipline, message quality, and anti-patterns
- Create atomic commit for green state
- Return contract output
Completion Checks
- Only green changes committed
- Commit message is clear and descriptive
- No refactor or new behavior included
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.
- 1mo ago First seen · 39 lines · 36 tokens per session scan A f0677738825b
tdd-commit is a skill published in the GitHub repository mrlarson2007/copilot-tdd-harness (5 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 220 once invoked, about $0.0001 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
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
test-then-commit
Implements a small change and commits it. Use when the user asks for a quick fix with a commit.