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 Justinmendezai/The-Adam-Repo --skill tddgit clone --depth 1 https://github.com/Justinmendezai/The-Adam-RepoWrote 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/justinmendezai/the-adam-repo/tdd)<a href="https://agentmods.dev/skills/justinmendezai/the-adam-repo/tdd"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/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/justinmendezai/the-adam-repo/tdd"><img src="https://agentmods.dev/badge/skills/justinmendezai/the-adam-repo/tdd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.00656 |
| Opus 5.5 | $0.00022 | $0.00262 |
| Sonnet 5.5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00066 |
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 2mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdd
Adapted from Matt Pocock's tdd. For direct work by the agent. (For orchestrated work, see tests-first, which inverts the roles — the orchestrator writes tests for subagents to satisfy.)
The loop
RED → write a failing test that captures the next slice of behavior
GREEN → write the minimum impl that makes it pass; nothing more
REFACTOR → clean up, factor, name well, while green stays green
One small slice per loop. Never write more impl than the current red test demands.
When to use
- New behavior with a clear user-visible outcome.
- Bug fix that must not regress.
- Refactor where you want a safety net before touching anything.
Workflow
1. Pick the smallest meaningful slice
If you can't think of a one-paragraph user-visible behavior, the slice is wrong. Re-cut.
2. RED
Write one test, not three. Make it specific. Run it. Confirm it fails for the right reason — not because of a missing import.
3. GREEN
Write the minimum code that makes it pass. Hardcode if you must. The next test will force generalization.
4. REFACTOR
Once green, look for:
- Duplication you can DRY (without adding wrong abstractions).
- Names that confuse on second reading.
- Long functions that have grown a natural seam.
Run the test after each refactor. If it goes red, you broke a contract. Revert.
5. Repeat
Add the next test. Repeat until the slice is done.
Test quality bar
- One assertion per test where possible.
- Test name reads like a sentence:
it("returns null when given an empty string"). - No mocking the system under test.
- No tests that pass-by-accident (test the failure path explicitly).
- No
beforeEachsetup that hides what's actually being tested.
When NOT to use TDD
- Spike / prototype work where you don't know what the output should look like. Use
prototypeinstead — write throwaway code, learn, then come back and TDD the real version. - One-shot scripts.
- Glue code with trivial logic and well-tested deps.
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.
- 2mo ago First seen · 76 lines · 54 tokens per session scan A 6e70d493270c
tdd is a skill published in the GitHub repository Justinmendezai/The-Adam-Repo (14 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 656 once invoked, about $0.0002 per session on Opus 5.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.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
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.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.