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 skills add devbyray/github-copilot-starter --skill testing-tddgit clone --depth 1 https://github.com/devbyray/github-copilot-starterWrote 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/devbyray/github-copilot-starter/testing-tdd)<a href="https://agentmods.dev/skills/devbyray/github-copilot-starter/testing-tdd"><img src="https://agentmods.dev/badge/skills/devbyray/github-copilot-starter/testing-tdd/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/devbyray/github-copilot-starter/testing-tdd"><img src="https://agentmods.dev/badge/skills/devbyray/github-copilot-starter/testing-tdd.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.00054 | $0.01014 |
| Opus 5.5 | $0.00022 | $0.00406 |
| Sonnet 5.5 | $0.00011 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
testing-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 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 189 lines · 54 tokens per session scan A 56e8f0c2506c
testing-tdd is a skill published in the GitHub repository devbyray/github-copilot-starter (5 stars, last pushed 8mo ago), with no licence file. It adds 54 tokens to every session and 1,014 once invoked, about $0.0002 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
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.
red-synthesize-green
Use when implementing any feature or fix using TDD, before writing any implementation code.
tdd-workflow
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle.
bad-case-to-dpo
A guide to turning failed production agent runs into training and evaluation data. It explains how to find the first mistake, create preference examples for DPO (Direct Preference Optimization), and check that a fix does not damage other tasks.
engineering-workflow
A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.
skill-tdd
Build a behavior change with observed red, minimal green, and measured test consolidation.