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 youdotcom-oss/dx-toolkit --skill tddgit clone --depth 1 https://github.com/youdotcom-oss/dx-toolkitWrote 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/youdotcom-oss/dx-toolkit/tdd)<a href="https://agentmods.dev/skills/youdotcom-oss/dx-toolkit/tdd"><img src="https://agentmods.dev/badge/skills/youdotcom-oss/dx-toolkit/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/youdotcom-oss/dx-toolkit/tdd"><img src="https://agentmods.dev/badge/skills/youdotcom-oss/dx-toolkit/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.00063 | $0.00652 |
| Opus 5.5 | $0.00025 | $0.00261 |
| Sonnet 5.5 | $0.00013 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
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.
This is a copy
88% identical to tdd — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test-Driven Development
Core Rule
Work in vertical red-green-refactor slices:
- RED: write one test for one observable behavior.
- GREEN: implement the smallest production change that makes that test pass.
- REFACTOR: clean up only while tests are green.
Do not write a batch of imagined tests before implementation. Each new test should respond to what the last cycle taught you about the actual behavior and interface.
Defaults
- Use
bun testfor targeted tests andbun run check:typesfor the type gate. - Use
test, notit, and organize withdescribe. - Prefer real dependencies and real runtime boundaries over mocks.
- Mock only external boundaries such as remote APIs, time, randomness, or rare filesystem cases.
- Avoid conditional assertions: assert the branch first, then assert branch-specific values.
- Test both branches for conditionals, fallbacks, and error paths.
- Prefer one stable public/runtime interface for each behavior. If the operator contract is a CLI, test the CLI boundary instead of splitting coverage across private helpers or duplicate wrappers.
- Exercise public interfaces and runtime contracts rather than private helpers.
- Follow applicable repo skills and
AGENTS.mdrules for the touched area.
When Starting Work
Explore the codebase first. If the public interface, expected behavior, or risk boundary is discoverable from code, tests, or docs, use that evidence instead of asking the user.
Ask one concise question only when the decision cannot be discovered and a reasonable assumption would be risky. Include your recommended answer.
Before writing production code, identify:
- the public interface or runtime boundary under test
- the first observable behavior to prove
- the targeted test command for the cycle
- the broader validation needed before handoff
Cycle Discipline
For each behavior:
- Add or update exactly one focused test.
- Run the targeted test and confirm it fails for the intended reason.
- Implement only enough code to pass.
- Run the same targeted test and confirm it passes.
- Refactor if useful, then rerun the affected tests.
What ships with it
5 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.
- 1mo ago First seen · 68 lines · 63 tokens per session scan A 201e3cab084c
tdd is a skill published in the GitHub repository youdotcom-oss/dx-toolkit (25 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 652 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to tdd, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
tests-run
Execute Unity tests (EditMode or PlayMode) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.
opik-compare
Run a candidate against the baseline over an Opik test suite and read the numbers back — which cases broke, which got fixed, the per-metric deltas, worst rows, and whether the two runs are comparable — with the Opik compare-view link. Runs via the SDK; reads results via the MCP when connected. Does not issue a…
opik-test
Turn a failing Opik trace (or a described failure) into a repeatable regression check — a test-suite item with the trace's input and one or two binary assertions — so a fix can be verified by the compare skill. Works over the SDK; uses the MCP write tool when connected. Returns the suite, the item, and the assertion.…
opik-verify
Decide ship or hold for a candidate from the compare skill's numbers, against an explicit release policy — regressions, pass rate, safety-tagged cases, subgroup consistency, latency and cost budgets, flakiness, evidence size, and whether the judge is validated. Reads two experiments on an Opik test suite via the SDK…
qec-memory-experiment
A local simulation workflow for testing error correction in a small surface-code quantum memory. It adds a defined error rate, samples measurement results, and uses a matching decoder to estimate logical errors.
quantum-circuit-verification
A local checker for deciding whether two small OpenQASM 2 quantum circuits perform the same quantum transformation. OpenQASM 2 is a text format for describing quantum circuits.