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 kimtth/agent-skill-100-lines-or-less --skill test-driven-developmentgit clone --depth 1 https://github.com/kimtth/agent-skill-100-lines-or-lessWrote 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/kimtth/agent-skill-100-lines-or-less/test-driven-development)<a href="https://agentmods.dev/skills/kimtth/agent-skill-100-lines-or-less/test-driven-development"><img src="https://agentmods.dev/badge/skills/kimtth/agent-skill-100-lines-or-less/test-driven-development/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/kimtth/agent-skill-100-lines-or-less/test-driven-development"><img src="https://agentmods.dev/badge/skills/kimtth/agent-skill-100-lines-or-less/test-driven-development.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.00028 | $0.00228 |
| Opus 5 | $0.00014 | $0.00114 |
| Sonnet 5 | $0.00006 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
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 8d 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.
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 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.
- 8d ago First seen · 31 lines · 28 tokens per session scan A 00641024b0cb
test-driven-development is a skill published in the GitHub repository kimtth/agent-skill-100-lines-or-less (2 stars, last pushed 2mo ago), with no licence file. It adds 28 tokens to every session and 228 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
skill-testing
AL test development patterns for Business Central. Use when creating test codeunits, writing Given/When/Then test procedures, using Library Assert, configuring test projects, or implementing TDD workflows.
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
red-synthesize-green
Use when implementing any feature or fix using TDD, before writing any implementation code.
phoenix-test
Drive development and bug-fixing with tests where the test IS the objective phoenixsense gate. Write a failing test before the code, reproduce a bug with a test before fixing it, and let phoenixsense decide pass/fail — never "looks right". Use when implementing logic, fixing a bug, changing behavior, or when the user…
tdd-red-green-refactor
Strict red/green/refactor/simplify discipline for the /build command. Use when implementing any task in Phase 4. The agent must NOT write production code without a failing test recorded in .tdd-state.json.