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 OneDro1d/dark-factory --skill df-tdd-developergit clone --depth 1 https://github.com/OneDro1d/dark-factoryWrote 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/onedro1d/dark-factory/df-tdd-developer)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/df-tdd-developer"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-tdd-developer.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.00072 | $0.01192 |
| Opus 5 | $0.00036 | $0.00596 |
| Sonnet 5 | $0.00014 | $0.00238 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
df-tdd-developer 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dark Factory — TDD Developer
Overview
Build every service test-first: RED → GREEN → REFACTOR, one case at a time. Each test is an executable validation rule. The Developer owns unit + integration tests (green before handoff); QA owns E2E + holdout.
The loop
| Step | Do | Done when |
|---|---|---|
| RED | Pick one case. Write the smallest test that encodes it. Run it — it fails. | Fails for the right reason (missing behaviour, not a typo). |
| GREEN | Write the minimal code to pass. Honour the contract; no extra features. | New test passes, all existing tests still green. |
| REFACTOR | Improve structure (names, duplication, size) without changing behaviour. Re-run after each change. | Still green, cleaner. A red test = you changed behaviour → undo. |
Where the test list comes from (don't invent it)
- LOCAL validation rule → unit test: feed bad input at the edge, assert it is rejected.
- GLOBAL validation rule → integration/reconciliation test: assert the invariant + the
authoritytie-break. - PO Test Scenario (
State 0 → Trigger → State 1) → unit/integration test asserting the end state (happy/edge/failure). - effect transform → idempotency test (replay → one action) + compensation test (failure → clean rollback).
- pure transform → plain input → output unit test.
Blind synthesis (anti-Goodhart)
Your own tests drive your build loop, but the acceptance evidence (PO Test Scenarios, the QA held-back acceptance suite) is withheld from you — you're verified against cases you never saw, which proves you built the spec, not your own test. Don't build to the holdout: if known_input: return known_answer is the lookup-degeneration failure.
GREEN discipline
Minimal code only; honour the exact contracts (no invented schemas); Log.Warn not Log.Error (panics in this stack's shared messaging library); decimal for money; config over code.
⚠️ That logging rule is an instance, not a universal. Some libraries escalate an
error-level call into a panic or a process exit, so a defensive Log.Error in a handler takes
the service down on the first bad message — the opposite of what the author meant. Others do
nothing of the kind. Check what your own stack does and write the answer into your own
guidance; the rule above is kept because a reader who follows it on a stack that behaves this
way is saved, and one who does not know to ask is not.
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 First seen · 86 lines · 72 tokens per session scan A babffaf6f320
df-tdd-developer is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 1,192 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-09-01.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
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.
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…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.