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/mickeyyaya/evolve-loop/tddnpx skills add mickeyyaya/evolve-loop --skill tddgit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWrote 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/mickeyyaya/evolve-loop/tdd)<a href="https://agentmods.dev/skills/mickeyyaya/evolve-loop/tdd"><img src="https://agentmods.dev/badge/skills/mickeyyaya/evolve-loop/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.00047 | $0.00677 |
| Opus 5 | $0.00023 | $0.00338 |
| Sonnet 5 | $0.00009 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00068 |
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 2d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tdd
Sprint 3 composable skill. Wraps the existing TDD-engineer phase with addyosmani-style structure. Mandatory hop before
build.
When to invoke
- After
plan-reviewreturns PROCEED, OR after Scout if plan-review disabled - Before any new feature implementation
- Before any bug fix (write a regression test first)
When NOT to invoke
- Eval-only cycles (no implementation needed)
- Pure documentation cycles
- Refactor cycles where existing tests provide coverage (verify first)
Workflow
| Step | Action | Exit criteria |
|---|---|---|
| 1 | Read scout-report.md and plan-review.md | Inputs verified |
| 2 | Write RED tests (must fail on current code) | Tests exist; running them fails |
| 3 | Document the test contract in <workspace>/tdd-contract.md |
Contract written |
| 4 | Append section to <workspace>/team-context.md |
Bus updated for Builder |
RED requirement
Tests MUST fail when run against the current codebase. A test that passes immediately is NOT a TDD contract — it does not exercise the new behavior. Builder will refuse to start without confirmed RED state.
Handoffs (beyond the contract artifact)
<workspace>/tdd-contract.mdwith sections:## Tests Written,## RED Verification,## Contract for Builder- New/modified test files in the repo (Builder reads these)
<workspace>/team-context.mdhas populated## TDD Contractsection
Phase facts
| Fact | Value |
|---|---|
| Phase | tdd (plan archetype, optional, gated by workflow.phase_enables.tdd=on) |
| Persona | agents/evolve-tdd-engineer.md |
| Profile | .evolve/profiles/tdd-engineer.json — CLI claude-tmux, tier balanced, single-writer |
| Inputs | scout-report.md · plan-review-report.md |
| Artifact | test-report.md (cycle workspace) |
Output contract
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.
- 2d ago First seen · 72 lines · 47 tokens per session scan A e3a6a2b0dbc9
tdd is a skill published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 677 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-09-03.
Other skills, from other repositories
testing-principles
Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.
unbiased-review
Use when reviewing a spec, plan, or implementation produced by another session - verifies its claims against the actual repo, grades TDD and hexagonal discipline, and reports severity-ranked findings without writing the fix. Triggers on "review this spec/plan/implementation", "second opinion on", "check this design"…
execute
Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.
testing-guide
GenAI-first testing with structural assertions, congruence validation, and tier-based test structure. Use when writing tests, setting up test infrastructure, or validating coverage. TRIGGER when: test, pytest, coverage, TDD, test patterns, congruence, validation. DO NOT TRIGGER when: production code implementation…
testing-new-code
Use when adding or modifying business logic, branching code, public API, or fixing a bug in a repo using repo-hygiene — tests for the new code paths must exist before the change is committed, not "later" or "if the user asks".
sw-build
TDD implementation of one work unit. Delegates test writing to the tester agent and implementation to the executor agent. Commits per task.