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/opendigitalproductfactory/opendigitalproductfactory/dpf-tddnpx skills add OpenDigitalProductFactory/opendigitalproductfactory --skill dpf-tddgit clone --depth 1 https://github.com/OpenDigitalProductFactory/opendigitalproductfactoryWhat 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.00041 | $0.01258 |
| Opus 5 | $0.00020 | $0.00629 |
| Sonnet 5 | $0.00008 | $0.00252 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
dpf-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 today.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DPF Test-Driven Development
Red-green-refactor is assumed, not taught. The DPF layer is that a test is evidence: the build gate enforces it at merge, and the kernel forbids claiming a green you did not observe.
When to use
- New behavior whose expected output is specifiable up front.
- Fixing a bug or regression — the highest-value case. The first-failing test is what proves the fix closed the symptom.
- Hardening a contract (schema, API shape, enum) against drift.
Skip it for a spike where the interface is still unknown, or a throwaway diagnostic with no merge path.
Run the test against the runtime it needs
- Source-local (targeted Vitest specs, typechecks, pure functions) — run in the thread worktree.
- Runtime-bound (needs the portal up, dev DB seeded, MCP reachable, Prisma generated, Build Studio executing) — run against the canonical local install or a governed shared nonprod environment (
dpf-use-shared-nonprod-environment).
This is AGENTS.md §4 "Where each gate runs" applied to TDD. Do not turn the worktree into a full DPF runtime so a runtime-bound test will run there — that is harness work, not test work.
A suite that did not execute because the worktree could not host its runtime is an unrun gate, not a red gate. Say which one you have.
The DPF-gated loop
- Impact before Red. Consume the
changeImpactContractreturned when the Workroom claimed its edit paths (or readverificationState.changeImpactContract). Resolve everytestImpactentry withfind_related_testsand pull everyguardObligationinto the loop now. Iffind_related_testsreturnsCode graph unavailable, an unavailable graph, or low-trust/qualify advice, do not retry it blindly: record the lookup as unavailable/unrun, then use a boundedGrep/Globsweep plus colocated tests and the repository's explicit test commands.status: unresolved, stale graph advice, or an unmapped source path expands verification — it never means "no tests." The fallback is evidence of the search you performed, not a claim that the graph found nothing.
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.
- today Changed 321127993179
- yesterday First seen · 74 lines · 41 tokens per session scan A d2964680dab4
dpf-tdd is a skill published in the GitHub repository OpenDigitalProductFactory/opendigitalproductfactory (14 stars, last pushed today), licensed Apache-2.0. It adds 41 tokens to every session and 1,258 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-30.
Other skills, from other repositories
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-benchmark-suite
Agent skill for benchmark-suite - invoke with $agent-benchmark-suite.
agent-migration-plan
Agent skill for migration-plan - invoke with $agent-migration-plan.
agent-performance-monitor
Agent skill for performance-monitor - invoke with $agent-performance-monitor.
agent-consensus-coordinator
Agent skill for consensus-coordinator - invoke with $agent-consensus-coordinator.
agent-mesh-coordinator
Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator.