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 DDS-Solutions/AI-TadPole-OS --skill tdd-workflowgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/tdd-workflow)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/tdd-workflow"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/tdd-workflow/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/dds-solutions/ai-tadpole-os/tdd-workflow"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/tdd-workflow.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.00031 | $0.01212 |
| Opus 5.5 | $0.00012 | $0.00485 |
| Sonnet 5.5 | $0.00006 | $0.00242 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
tdd-workflow 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 7d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / tdd-workflow
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Writing implementation code before writing failing tests, untested regression paths, or unverified green transitions.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Test-Driven Development (TDD) Protocol
Philosophy: Write tests first, code second. Prove failure before implementing solutions. The test is the deterministic contract of truth.
Workflow Bindings: Integrated directly into/test,/create, and/debug.
🎯 Progressive Disclosure & L3 Reference Index
Read the core Sovereign rules below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide | Purpose | Trigger / When to Load |
|---|---|---|
references/tdd_patterns_and_cycles.md |
Concrete code cycles, Three Laws of TDD, test smell refactoring | Writing unit tests before implementation |
scripts/tdd_cycle_guard.py |
Automated TDD state-machine tracking Red-Green-Refactor phase transitions | Enforcing and recording TDD cycles |
🔄 1. The RED-GREEN-REFACTOR Cycle
[1. 🔴 RED] ─────────────> [2. 🟢 GREEN] ─────────────> [3. 🔵 REFACTOR]
Write a minimal failing Write the minimum code Clean up code, remove
test asserting behavior required to pass the test duplication, stay green
- 🔴 RED: Write a minimal, expressive test asserting the desired behavior. Run it and verify that it fails (exit code $\ne 0$). Record via
tdd_cycle_guard.py --record-phase RED. - 🟢 GREEN: Write the simplest implementation code that satisfies the test. Run the test and verify it passes (exit code $0$). Record via
tdd_cycle_guard.py --record-phase GREEN. - 🔵 REFACTOR: Clean up syntax, remove duplication, and optimize algorithms while ensuring tests remain green.
What ships with it
2 files 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.
- 7d ago Changed · +32 lines · +10 tokens per session fb4e22fc9a4d
- 1mo ago First seen · 58 lines · 21 tokens per session scan A 174f83825482
tdd-workflow is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 1,212 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
server-side-calls
Call tRPC procedures directly from server code using t.createCallerFactory() and router.createCaller(context) for integration testing, internal server logic, and custom API endpoints. Catch TRPCError and extract HTTP status with getHTTPStatusCodeFromError(). Error handling via onError option.
fullstack-engineer
Consolidated web engineering skill combining backend and frontend development. Implements backend services, APIs, business logic, and web frontends (React/Next.js). Includes clean architecture, TDD, error handling, and state management patterns. Combines: software-engineer + frontend-engineer.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
tdd-cycle
Red-Green-Refactor TDD loop with mandatory false-positive check.
typescript-test-writing
Use this skill when writing or modifying tests in the llxprt-code repository. Covers mandatory TDD, behavioral testing, bun:test conventions and file naming, mock hygiene (no mock theater), and what never to test. Distilled from dev-docs/RULES.md, which remains the source of truth.
common-subagent-driven-development
Execute multi-task implementation plans by dispatching a fresh implementer subagent per task with independent review gates. Use when implementing plans, executing multi-task PRs, or transitioning from planning to implementation.