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/klausfreiberufler/devflow-mcp/devflow-tddnpx skills add KlausFreiberufler/devflow-mcp --skill devflow-tddgit clone --depth 1 https://github.com/KlausFreiberufler/devflow-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/klausfreiberufler/devflow-mcp/devflow-tdd)<a href="https://agentmods.dev/skills/klausfreiberufler/devflow-mcp/devflow-tdd"><img src="https://agentmods.dev/badge/skills/klausfreiberufler/devflow-mcp/devflow-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 | $0.00081 | $0.01134 |
| Opus 5 | $0.00041 | $0.00567 |
| Sonnet 5 | $0.00016 | $0.00227 |
| Haiku 4.5 | $0.00008 | $0.00113 |
Grade A, and why
devflow-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 3d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: devflow-tdd
Iron Law port of Superpowers
test-driven-development. The cycle is non-negotiable; this skill refuses to emit a token if any of the three iron laws were broken.
When to use
Use this skill in in_progress state for every code change that introduces or modifies behavior. Pure refactors that change nothing observable are exempt; everything else goes through RED → GREEN → REFACTOR.
Process
0 · Pull existing test-patterns (Hook 3)
Before writing the first test, query the LLM-Wiki for reusable test-pattern doc-pages tagged testing:
GET /api/projects/:projectId/docs?document_type=pattern&tag=testing
(equivalent MCP call: doc_page_list({ projectId, document_type: 'pattern', tags: ['testing'] }))
Cite each pattern that applies via wiki-link in the test file's leading comment, e.g.:
// Follows [[pattern:vitest-api-test-pattern]] — createApiClient + describe/it + cleanup
This keeps test conventions consistent across flows and surfaces the patterns in the Knowledge-Graph for future readers.
1 · RED — failing test first
- Write a single test that captures one behavioral expectation.
- Run the test suite. Confirm the new test fails for the expected reason (not a syntax error, not a missing import — the actual assertion).
- Capture the failure output.
2 · GREEN — minimum production code
- Add the smallest amount of production code that makes the new test pass.
- Re-run the suite. Confirm:
- The new test now passes.
- No previously-passing test broke.
3 · REFACTOR — only after GREEN
- Clean up the code (rename, dedupe, extract). Tests stay green throughout.
- Re-run the suite after every non-trivial refactor — never skip the safety check.
4 · Commit & repeat
- One commit per RED → GREEN → REFACTOR cycle (or grouped semantically when the cycles are tightly coupled).
- Then move to the next acceptance-criterion / task. Begin a fresh cycle at step 1.
Iron Laws
No production code without a failing test first.
REFACTOR happens only after GREEN.
One concern per RED-GREEN-REFACTOR cycle.
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.
- 3d ago First seen · 121 lines · 81 tokens per session scan A d34b60e8d681
devflow-tdd is a skill published in the GitHub repository KlausFreiberufler/devflow-mcp (1 stars, last pushed 5d ago), licensed MIT. It adds 81 tokens to every session and 1,134 once invoked, about $0.0004 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
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
tdd
Test-driven development (TDD) process used when writing code. Use whenever you are adding any new code, unless the user explicitly asks to skip TDD or the code is exploratory/spike.
growing-outside-in-systems
Drive feature development using Outside-In TDD with Hexagonal Architecture. Design emerges through inline code, in-memory fakes, interface extraction, and deferred I/O. Use when building features, writing tests, or structuring backend services. Triggers on: TDD, outside-in, hexagonal, ports and adapters, emergent…
plan-create
Create structured implementation plans for autonomous TDD development. Use for new features, multi-file changes, or anything requiring multiple steps or tests. Triggers on aspirational openers ("let's build", "let's start building", "I want to make", "I want an app that", "help me build"), capability lists ("users…
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like…