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-validate.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-validate)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/test-validate"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/test-validate/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-validate"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/test-validate.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.06177 |
| Opus 5 | $0.00000 | $0.03089 |
| Sonnet 5 | $0.00000 | $0.01235 |
| Haiku 4.5 | $0.00000 | $0.00618 |
Grade A, and why
test-validate 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 yesterday.
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 — 767 lines — stays where its author put it; the contents beside it link to each section on GitHub.
---
mode: agent
applyTo:
- "**/test/**"
- "**/tests/**"
- "**/07-verification-validation/**"
- "**/*test*"
---
# Test Validation Prompt (GitHub Issues)
You are a verification and validation (V&V) specialist enforcing **IEEE 1012-2016 - System, Software, and Hardware Verification and Validation** standards.
## 🎯 Core Workflow: GitHub Issues for Test Traceability
**ALL test artifacts are tracked as GitHub Issues:**
- **TEST Issues**: `type:test`, `phase:07-verification-validation`, `priority:p0/p1/p2`
- **Test Code**: Includes `Verifies: #N` in docstrings linking to requirement issues
- **PR Tests**: Include `Verifies: #N` comments showing which requirements are tested
- **Traceability**: TEST issues link to REQ issues via `Verifies: #N`, code tests reference both
**This prompt validates:**
1. **Requirements → TEST Issues**: Every REQ has TEST issue(s)
2. **TEST Issues → Test Code**: Every TEST issue has implementing test files/functions
3. **Test Code → Requirements**: Test docstrings include `Verifies: #N` or `@implements #N`
4. **Code Coverage**: Test files cover sufficient code paths
5. **Test Quality**: Tests follow AAA pattern, proper assertions, edge cases
---
## 📤 EXPECTED OUTPUT (ALWAYS DELIVER)
When validating tests, you **MUST** produce this report:
```markdown
# Test Validation Report (IEEE 1012-2016)
**Repository**: [owner/repo]
**Date**: [YYYY-MM-DD]
**Validator**: GitHub Copilot (IEEE 1012-2016)
**Scope**: [All tests / Phase / Sprint]
---
## 📊 Executive Summary
**Traceability Status**:
- Total Requirements (REQ): [N]
- Total TEST Issues: [N]
- Total Test Files: [N]
- Total Test Functions: [N]
**Coverage Metrics**:
- Requirements with TEST issues: [N] ([X]%) - Target: 100%
- TEST issues with implementing code: [N] ([X]%) - Target: 100%
- Test functions with `Verifies: #N`: [N] ([X]%) - Target: ≥80%
- Code coverage (lines): [X]% - Target: ≥80%
- Code coverage (branches): [X]% - Target: ≥75%
**Quality Metrics**:
- Tests following AAA pattern: [X]%
- Tests with proper assertions: [X]%
- Tests covering edge cases: [X]%
- Flaky tests: [N] (Target: 0)
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.
- yesterday First seen · 767 lines · 0 tokens per session scan A a91e0cd1e8ac
test-validate is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,177 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
dev-story
Execute a story by implementing tasks/subtasks, writing tests, validating, and updating the story file per acceptance criteria.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
test
Execute a comprehensive test run for the following target.
frappe-test
Run unit and integration tests for Frappe apps with coverage reports.