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/yaomeng1749/claude-code-digital-nomad-config-pack/test-driven-developmentnpx skills add Yaomeng1749/claude-code-digital-nomad-config-pack --skill test-driven-developmentgit clone --depth 1 https://github.com/Yaomeng1749/claude-code-digital-nomad-config-packWrote 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/yaomeng1749/claude-code-digital-nomad-config-pack/test-driven-development)<a href="https://agentmods.dev/skills/yaomeng1749/claude-code-digital-nomad-config-pack/test-driven-development"><img src="https://agentmods.dev/badge/skills/yaomeng1749/claude-code-digital-nomad-config-pack/test-driven-development.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 | $0.00017 | $0.02406 |
| Opus 5 | $0.00009 | $0.01203 |
| Sonnet 5 | $0.00003 | $0.00481 |
| Haiku 4.5 | $0.00002 | $0.00241 |
Grade A, and why
test-driven-development 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 yesterday.
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 ships with it
1 file 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.
- yesterday First seen · 372 lines · 17 tokens per session scan A 7dee67b4af6b
test-driven-development is a skill published in the GitHub repository Yaomeng1749/claude-code-digital-nomad-config-pack (4 stars, last pushed 4mo ago), with no licence file. It adds 17 tokens to every session and 2,406 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-09-03.
Other skills, from other repositories
ag-referencia-tdd
TDD canonico Red-Green-Refactor — pipeline obrigatorio teste-primeiro. Reference skill carregada on-demand pelo modo --tdd da ag-1-construir.
pdlc-feature
全自动 PDLC 新功能开发（串联 PRD→设计→TDD→实现→评审→发布）.
tdd
Use when running the full Rails TDD loop: failing spec, implement, review, PR. Trigger words: TDD, red-green-refactor, write tests first, test-driven.
tdd
Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when implementing a feature or fixing a bug where correctness matters and a test can pin the behavior. Says "TDD", "test first", "red green refactor", "write the test first".
refactor-code-with-ai
Refactor code with AI assistance. Use to refactor code in TDD loop, and to improve code quality.
plan-to-tdd
Transform feature plans into test-driven implementation using Outside-In methodology. This skill should be used when converting documented plans from docs/plan/ into testable code w/ proper test structure (Unit, Integration, E2E).