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 Shelpuk-AI-Technology-Consulting/agent-skill-tdd --skill tddgit clone --depth 1 https://github.com/Shelpuk-AI-Technology-Consulting/agent-skill-tddWrote 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/shelpuk-ai-technology-consulting/agent-skill-tdd/tdd)<a href="https://agentmods.dev/skills/shelpuk-ai-technology-consulting/agent-skill-tdd/tdd"><img src="https://agentmods.dev/badge/skills/shelpuk-ai-technology-consulting/agent-skill-tdd/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/shelpuk-ai-technology-consulting/agent-skill-tdd/tdd"><img src="https://agentmods.dev/badge/skills/shelpuk-ai-technology-consulting/agent-skill-tdd/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.00059 | $0.01880 |
| Opus 5 | $0.00030 | $0.00940 |
| Sonnet 5 | $0.00012 | $0.00376 |
| Haiku 4.5 | $0.00006 | $0.00188 |
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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working Agreement
This skill is intentionally always-on for coding tasks. Follow it exactly unless the user explicitly opts out.
Non-negotiables
- Serena first: Start by activating the Serena project (if the Serena tools exist in the environment). If activation fails for reasons outside your control, continue without Serena and say why.
- Investigate before changing anything: Understand the current state (application state, execution results, user input, logs) before proposing edits.
- No requirement changes without confirmation: If requirements are unclear, ask clarifying questions. Before you change/add/interpret requirements, get explicit confirmation.
- Create a per-task
REQUIREMENTS.mdbefore implementation:- Create/use root
.requirements/. - For each task, choose a short snake_case feature name using lowercase ASCII letters, digits, and underscores only (for example,
update_github_authentication). - Create a folder named
<datetime>_<feature_name>using UTC datetime formatYYYYMMDDTHHMMSSZ(for example,20260301T143210Z_update_github_authentication). - If the folder already exists, append a numeric suffix (
_01,_02, and so on) to avoid collisions. Example:.requirements/20260301T143210Z_update_github_authentication_01/. - Write the task requirements file to
.requirements/<datetime>_<feature_name>/REQUIREMENTS.mdusing the mandated structure (below).
- Create/use root
- Use up-to-date docs: When you rely on an API/package/technology detail, use Kindly Web Search (if available) to confirm signatures, version behavior, breaking changes, and deprecations.
- Smallest possible steps (TDD): Implement one small change at a time and test each change (unit → integration → smoke as appropriate) before proceeding.
Per-task REQUIREMENTS.md Structure (Mandated)
For each task, write REQUIREMENTS.md to .requirements/<datetime>_<feature_name>/REQUIREMENTS.md with:
- As Is: current behavior/state (what exists today).
- To Be: desired behavior/state after the change.
- Requirements: functional requirements (numbered).
- Acceptance Criteria: for every functional requirement, add explicit acceptance criteria.
- Testing Plan: test strategy + cases (TDD best practices).
- Implementation Plan: the smallest sequential code changes; for each change, include how you’ll test it.
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 · 159 lines · 59 tokens per session scan A 8500b3138dfa
tdd is a skill published in the GitHub repository Shelpuk-AI-Technology-Consulting/agent-skill-tdd (30 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 1,880 once invoked, about $0.0003 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-30.
Other skills, from other repositories
test-driven-execution
Before writing any implementation code, define the acceptance criteria and test cases that the code must satisfy. Agents then write code to pass these tests — not to match a vague description. Eliminates "it works on my machine" and "I think this is what you wanted" outcomes.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd-practitioner
Practice Test-Driven Development with the red-green-refactor cycle. Write tests before code to drive better design, coverage, and confidence.
python-testing-patterns
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
tdd-full-cycle
Group skill: Test-Driven Development full cycle — plan, RED phase, GREEN phase, REFACTOR phase, E2E tests, coverage, and review.
bats-testing-patterns
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.