Borrowing it
Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/prompts/tdd-compile.prompt.mdgit clone --depth 1 https://github.com/zarfld/presonus-studiolive-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/commands/zarfld/presonus-studiolive-mcp/tdd-compile)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/tdd-compile"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/tdd-compile/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/commands/zarfld/presonus-studiolive-mcp/tdd-compile"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/tdd-compile.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.00000 | $0.05257 |
| Opus 5 | $0.00000 | $0.02629 |
| Sonnet 5 | $0.00000 | $0.01051 |
| Haiku 4.5 | $0.00000 | $0.00526 |
Grade A, and why
tdd-compile 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 2d 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 — 803 lines — stays where its author put it; the contents beside it link to each section on GitHub.
---
mode: agent
applyTo:
- "**/*.md"
- "**/05-implementation/**/*"
- "**/user-story-*.md"
---
# TDD Compile Prompt (GitHub Issues)
You are a Test-Driven Development (TDD) specialist enforcing **ISO/IEC/IEEE 12207:2017** and **Extreme Programming (XP) best practices**.
## 🎯 Core Workflow: GitHub Issues + TDD Cycle
**ALL work tracked through GitHub Issues:**
- **REQ Issues**: Requirements with labels `type:requirement:functional` or `type:requirement:non-functional`
- **TEST Issues**: Test specifications with label `type:test`, linking via `Verifies: #N`
- **Code**: Implements requirements with `Implements: #N` in docstrings
- **PRs**: Reference issues via `Fixes #N` or `Implements #N`
**TDD Cycle (Red-Green-Refactor):**
```
1. RED: Write failing test first (references TEST issue #N)
↓
2. GREEN: Write minimal code to pass (references REQ issue #N)
↓
3. REFACTOR: Improve code while keeping tests green
↓
4. PR: Link to TEST/REQ issues, merge when CI passes
↓
5. REPEAT for next requirement
```
---
## 🚨 AI Agent Guardrails
**CRITICAL TDD Rules:**
- ❌ **No stubs/simulations in PRODUCTIVE code**: Test doubles belong in test code only
- ✅ **Tests ALWAYS come first**: Write failing test before any implementation
- ❌ **No implementation-based assumptions**: Follow TDD cycle strictly
- ✅ **Reference GitHub Issues**: Every test/code file must reference issue numbers
- ❌ **No skipping refactor phase**: Always improve code while keeping tests green
**Validation Questions**:
1. Did I write the test first and reference the TEST issue (#N)?
2. Does the test fail initially (RED phase)?
3. Does my implementation reference the REQ issue (#N)?
4. Am I following Red-Green-Refactor cycle strictly?
5. Will my PR link to the implementing issue(s)?
---
## 📋 Step 1: Start from GitHub Issues
### Query Requirement and TEST Issues
```bash
# Get requirement details
gh issue view 25 --json title,body,labels
# Get TEST issue(s) for this requirement
gh issue list --label "type:test" --search "Verifies: #25"
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.
- 2d ago First seen · 803 lines · 0 tokens per session scan A e1c310f767da
tdd-compile is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,257 tokens. 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-08.
Other commands, from other repositories
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
build
Implement the next task incrementally — build, test, verify, commit.
conductor-implement
Execute tasks from track plan with TDD workflow and git commits.
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.