presonus-studiolive-mcp: Command for GitHub Copilot

.github/prompts/test-gap-filler.prompt.md

test-gap-filler is a command for GitHub Copilot from zarfld/presonus-studiolive-mcp. It costs 0 tokens per session (5,159 once invoked), scanned A, original, MIT.

A test-gap finder that compares requirements recorded in GitHub Issues with test specifications and test code.

In plain words
What is it for?
Use it to create missing test issues and test code, add requirement references, and produce coverage and gap reports.
Why use it?
It helps reveal requirements that have no test issue, no implementing test code, or no clear link between the requirement and its tests.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

This is zarfld/presonus-studiolive-mcp's own configuration. It tells GitHub Copilot how to work on presonus-studiolive-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything presonus-studiolive-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/prompts/test-gap-filler.prompt.md
Clone the repo
git clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcp

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for test-gap-filler

README.md
[![agentmods](https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/test-gap-filler/github.svg)](https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/test-gap-filler)
Your own site
<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.

agentmods 80×15 button for test-gap-filler

Your own site · 80×15
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,159 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 4f286a2798a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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.

.github/prompts/test-gap-filler.prompt.md · 693 lines

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')

Read the full file on GitHub · 693 lines

Changes

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.

  1. 3d ago First seen · 693 lines · 0 tokens per session scan A 4f286a2798a4

Subscribe to this mod's changes

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.