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 Eilodon/DPS-Superskills-MCP --skill tdd-verifiedgit clone --depth 1 https://github.com/Eilodon/DPS-Superskills-MCPWrote 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/eilodon/dps-superskills-mcp/tdd-verified)<a href="https://agentmods.dev/skills/eilodon/dps-superskills-mcp/tdd-verified"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/tdd-verified/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/eilodon/dps-superskills-mcp/tdd-verified"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/tdd-verified.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.00049 | $0.01666 |
| Opus 5 | $0.00024 | $0.00833 |
| Sonnet 5 | $0.00010 | $0.00333 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
tdd-verified 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 10d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TDD-Verified — Proof-First Development with Evidence Anchors
Register: DISCIPLINE — Iron Laws apply. Non-negotiable.
This skill enforces proof-first development. For behavior code and bug fixes, the default proof mode is RED-GREEN-REFACTOR with VHEATM evidence anchors at every gate. For migrations, config, docs, or spikes, declare an alternate proof mode before implementation.
Core principle: Evidence before claims. If you didn't watch the test fail, you don't know if it tests the right thing. If you didn't run verification, you cannot claim it passes.
Violating the letter of these rules is violating their spirit.
The Iron Laws
1. NO IMPLEMENTATION WITHOUT A DECLARED PROOF MODE
2. NO BEHAVIOR CODE WITHOUT A FAILING TEST FIRST
3. NO COMPLETION CLAIM WITHOUT FRESH VERIFICATION EVIDENCE
4. NO FIX CLAIM WITHOUT A FIX ANCHOR (file:line re-read after change)
For behavior code, writing code before the failing test means delete it and start over. For other work, the declared proof mode defines the evidence gate.
Proof Mode Declaration
Declare one before implementation:
| Proof mode | Use when | Required evidence |
|---|---|---|
| TEST_FIRST | behavior code, feature logic, bug fixes | failing test observed first, then passing test/suite |
| MIGRATION_DRY_RUN | schema/data migration, backfill | dry-run output, backup/rollback or accepted irreversibility, checksum/count plan |
| CONFIG_SMOKE | config, routing, deployment settings | config diff, smoke command, environment-specific verification |
| DOC_SOURCE_CHECK | README/spec/docs claims | source cross-check against code/spec/ADR; label unverified claims T4 |
| SPIKE_THROWAWAY | exploratory prototype | timeboxed learning, explicit throwaway status; cannot ship until converted to another proof mode |
No completion claim is allowed until the proof mode has T1/T2 evidence.
RED-GREEN-REFACTOR with Evidence Gates
RED — Write Failing Test
Write one minimal test showing exactly what should happen.
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.
- 10d ago First seen · 183 lines · 49 tokens per session scan A 171c326c2ef3
tdd-verified is a skill published in the GitHub repository Eilodon/DPS-Superskills-MCP (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,666 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-08-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
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.