Borrowing it
Nothing to install: this file belongs to iamadi11/mcp-ui-poc. 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/iamadi11/mcp-ui-poc/main/.claude/skills/tdd/SKILL.mdgit clone --depth 1 https://github.com/iamadi11/mcp-ui-pocWrote 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/iamadi11/mcp-ui-poc/tdd)<a href="https://agentmods.dev/skills/iamadi11/mcp-ui-poc/tdd"><img src="https://agentmods.dev/badge/skills/iamadi11/mcp-ui-poc/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/iamadi11/mcp-ui-poc/tdd"><img src="https://agentmods.dev/badge/skills/iamadi11/mcp-ui-poc/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.00016 | $0.00172 |
| Opus 5 | $0.00008 | $0.00086 |
| Sonnet 5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
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 10d 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 (test-driven)
Testing policy: docs/AI_WORKFLOW.md → Testing expectations.
Steps
- Confirm whether automated tests exist for the area (this repo: client ESLint; no root test runner yet).
- If adding a test framework: add dependency, script, and one minimal test in the same effort — then implement to green.
- Until automated tests exist: maintain a manual test checklist (steps + expected result) before merging behavior changes.
- After implementation, re-run lint (
client/) and manual validation.
Checklist
- Failing case or checklist exists before “done.”
- No secrets in test fixtures or logs.
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.
- 10d ago First seen · 21 lines · 16 tokens per session scan A 81f1c7a36e16
tdd is a skill published in the GitHub repository iamadi11/mcp-ui-poc (8 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 172 once invoked, about $0.0001 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.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
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.
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.