presonus-studiolive-mcp: Command for GitHub Copilot

.github/prompts/requirements-validate.prompt.md

requirements-validate is a command for GitHub Copilot from zarfld/presonus-studiolive-mcp. It costs 0 tokens per session (4,948 once invoked), scanned A, original, MIT.

A requirements review command for checking GitHub Issues, which are online project records used to track work and specifications, against ISO/IEC/IEEE 29148 requirements guidance.

In plain words
What is it for?
Use it to review stakeholder and system requirements in GitHub Issues and create a validation report with compliance findings.
Why use it?
It helps expose requirements that are incomplete, contradictory, technically unclear, hard to test, or missing measurable acceptance criteria and links to related work.

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/requirements-validate.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 requirements-validate

README.md
[![agentmods](https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-validate/github.svg)](https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/requirements-validate)
Your own site
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/requirements-validate"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-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.

agentmods 80ร—15 button for requirements-validate

Your own site ยท 80ร—15
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/requirements-validate"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-validate.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 4,948 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.04948
Opus 5 $0.00000 $0.02474
Sonnet 5 $0.00000 $0.00990
Haiku 4.5 $0.00000 $0.00495

Measured 2d ago against content hash 7f4e26e15ec9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

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

.github/prompts/requirements-validate.prompt.md ยท 629 lines

How it starts

The opening of the file, as written. The whole thing โ€” 629 lines โ€” stays where its author put it; the contents beside it link to each section on GitHub.

---
mode: agent
applyTo:
  - "**/*requirements*.md"
  - "**/02-requirements/**/*.md"
  - "**/stakeholder-requirements*.md"
---

# Requirements Validation Prompt (GitHub Issues)

You are a requirements validation specialist enforcing **ISO/IEC/IEEE 29148:2018** standards using **GitHub Issues** as the requirements management system.

## ๐ŸŽฏ Objective

Validate GitHub Issues (StR, REQ-F, REQ-NF) for compliance with ISO 29148:2018 standards, checking:
- **Completeness**: All required fields present
- **Consistency**: No conflicting requirements
- **Correctness**: Technically accurate and feasible
- **Testability**: Verifiable acceptance criteria
- **Traceability**: Proper issue links (#N syntax)
- **Measurability**: Quantifiable for NFRs

## ๐Ÿ“ค EXPECTED OUTPUT (ALWAYS DELIVER)

```markdown
# Requirements Validation Report

**Repository**: [owner/repo-name]
**Date**: [YYYY-MM-DD]
**Validator**: GitHub Copilot (ISO/IEC/IEEE 29148:2018)
**Issues Analyzed**: [N] issues

---

## ๐Ÿ“Š Executive Summary

**Compliance Score**: [XX]% (Target: 95%+)
**Certification Status**: โœ… ISO 29148 Compliant / โš ๏ธ Needs Work / ๐Ÿ”ด Not Compliant

| Validation Type | Pass | Fail | Score |
|----------------|------|------|-------|
| Completeness | [N] | [N] | [XX]% |
| Consistency | [N] | [N] | [XX]% |
| Correctness | [N] | [N] | [XX]% |
| Testability | [N] | [N] | [XX]% |
| Traceability | [N] | [N] | [XX]% |
| Measurability (NFRs) | [N] | [N] | [XX]% |

**Overall**: [N] issues valid, [N] with issues

---

## ๐Ÿ”ด Critical Issues (Must Fix)

### Issue #[N]: [Title]
**Issue Type**: StR / REQ-F / REQ-NF
**Problem**: [Completeness/Consistency/Correctness/Testability/Traceability/Measurability]
**ISO 29148 Reference**: ยง [section]
**Severity**: ๐Ÿ”ด Critical

**Detailed Problem**:
[Specific issue description]

**Impact**:
[Why this blocks progress or violates standards]

**Required Fix**:
1. Edit issue #[N]
2. Update [specific section]
3. Add/fix: [specific content]

**Example Fix**:
```markdown
## Traceability
- Traces to:  #[parent-issue]
- **Depends on**: #[prereq-issue]
```

Read the full file on GitHub ยท 629 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. 2d ago First seen ยท 629 lines ยท 0 tokens per session scan A 7f4e26e15ec9

Subscribe to this mod's changes

requirements-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 4,948 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.