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 agentmods add skills/ntaffzii/skill-agents/tddnpx skills add ntaffzii/Skill-Agents --skill tddgit clone --depth 1 https://github.com/ntaffzii/Skill-AgentsWrote 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/ntaffzii/skill-agents/tdd)<a href="https://agentmods.dev/skills/ntaffzii/skill-agents/tdd"><img src="https://agentmods.dev/badge/skills/ntaffzii/skill-agents/tdd.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.00043 | $0.00472 |
| Opus 5 | $0.00022 | $0.00236 |
| Sonnet 5 | $0.00009 | $0.00094 |
| Haiku 4.5 | $0.00004 | $0.00047 |
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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD
Use this skill to make behavior changes with a tight feedback loop.
Workflow
-
Clarify behavior
- Identify the user-visible behavior, input, output, and edge cases.
- Find the smallest vertical slice that proves the behavior.
- If the request is ambiguous, make a conservative assumption and state it.
-
Find the test seam
- Prefer the seam closest to real behavior: integration, API, component, e2e, then unit.
- Avoid tests that only assert implementation details.
- If no useful seam exists, note that as design pressure and choose the best available signal.
-
Red
- Write one failing test for the next slice.
- Run only the narrowest relevant test command first.
- Confirm the failure is for the expected reason.
-
Green
- Implement the smallest change that passes the test.
- Keep changes scoped to the behavior under test.
- Do not refactor unrelated code during green.
-
Refactor
- Improve clarity only after the test passes.
- Preserve behavior and rerun the relevant tests.
- Remove duplication only when it is real and local.
-
Expand
- Add edge cases only after the core path works.
- Repeat red-green-refactor for each slice.
- Finish by running the broader relevant suite.
Test Quality Rules
- A good test fails before the fix and passes after it.
- Test names should describe behavior, not implementation.
- Do not mock the thing being tested.
- Prefer fixtures over hand-built objects when local patterns already use fixtures.
- Keep assertions specific enough to catch the bug or behavior contract.
Verification
- The new or changed test fails before the implementation when practical.
- The focused test command passes after the implementation.
- A broader relevant suite passes when the change touches shared behavior.
- Untested risk is named when broader validation is not practical.
Completion Report
End with:
- Behavior implemented
- Tests added or changed
- Commands run
- Any untested risk
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.
- 6d ago First seen · 65 lines · 43 tokens per session scan A 0132774d6e06
tdd is a skill published in the GitHub repository ntaffzii/Skill-Agents (4 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 472 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
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
test-generation
Use when the user asks for tests, mentions TDD, or when new code has been written and needs test coverage.
setup
Set up or update TDD Guard for the current project. Detects the test framework, installs or updates the matching reporter, and configures or migrates its configuration to match the current specification.
taiyi-dev
TaiyiForge 第6阶段 — TDD开发执行。四端通用。.
acceptance
End-to-end verification and self-evidence for a delivery in any repository, with or without a preconfigured verify plan. Discover an existing plan when one was handed to this run; otherwise author checks and publish a standalone acceptance. Pick the proving surface (CLI / web / desktop / iOS Simulator), drive the real…