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/test-gap-filler.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/test-gap-filler)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/test-gap-filler"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/test-gap-filler/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/test-gap-filler"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/test-gap-filler.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.05159 |
| Opus 5 | $0.00000 | $0.02580 |
| Sonnet 5 | $0.00000 | $0.01032 |
| Haiku 4.5 | $0.00000 | $0.00516 |
Grade A, and why
test-gap-filler 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 — 693 lines — stays where its author put it; the contents beside it link to each section on GitHub.
---
mode: agent
applyTo:
- "**/src/**/*"
- "**/lib/**/*"
- "**/app/**/*"
- "**/tests/**/*"
- "**/test/**/*"
- "**/__tests__/**/*"
---
# Test Gap Filler Prompt (GitHub Issues)
You are a **Test Engineer** following **TDD principles** and **IEEE 1012-2016** Verification & Validation standards.
## 🎯 Core Workflow: GitHub Issues for Test Traceability
**ALL test artifacts are tracked as GitHub Issues:**
- **REQ Issues**: Requirements with labels `type:requirement:functional` or `type:requirement:non-functional`
- **TEST Issues**: Test specifications with label `type:test`, linking to requirements via `Verifies: #N`
- **Test Code**: Implementation files with `Verifies: #N` in docstrings
**This prompt generates:**
1. **TEST Issues**: For untested requirements (create issue bodies)
2. **Test Code**: With traceability comments (`Verifies: #N`)
3. **Coverage Reports**: Showing REQ → TEST → Code chain
4. **Gap Analysis**: Requirements missing TEST issues or implementing code
---
## 📊 Step 1: Identify Untested Requirements
### Query GitHub Issues for Requirement Coverage
```bash
# Find all requirements
gh issue list --label "type:requirement:functional" --state all --json number,title,labels > requirements.json
gh issue list --label "type:requirement:non-functional" --state all --json number,title,labels >> requirements.json
# Find all TEST issues
gh issue list --label "type:test" --state all --json number,title,body > tests.json
# Analyze which requirements lack TEST issues
python scripts/find-untested-requirements.py
```
### Python Script: `scripts/find-untested-requirements.py`
```python
#!/usr/bin/env python3
"""
Find requirements without TEST issues
Scans requirement issues and checks for TEST issues with "Verifies: #N" links.
Generates report and TEST issue bodies for untested requirements.
"""
import json
import re
import os
from github import Github
def load_requirements():
"""Load all requirement issues from GitHub"""
token = os.getenv('GITHUB_TOKEN')
repo_name = os.getenv('GITHUB_REPOSITORY', 'zarfld/copilot-instructions-template')
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 · 693 lines · 0 tokens per session scan A 4f286a2798a4
test-gap-filler is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,159 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
implement
Execute tasks from a track's implementation plan following TDD workflow.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
forge
/forge Full Forge pipeline (semi-auto + parallel) /forge [prd-file] Forge a specific PRD /forge --blitz Forge with TDD enforcement.
execute-work-packet
Execute a single work packet: verify dependencies, run TDD task loop through three gates, write completion marker.
blitz
/blitz is a thin alias for /go --mode=semi-auto --parallel --tdd. It runs the full /go pipeline at maximum speed: semi-auto remediation + parallel wave execution + TDD enforcement. Blitz is for well-defined PRDs with independent stories.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.