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/requirements-complete.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/requirements-complete)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/requirements-complete"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-complete/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/requirements-complete"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-complete.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.09960 |
| Opus 5 | $0.00000 | $0.04980 |
| Sonnet 5 | $0.00000 | $0.01992 |
| Haiku 4.5 | $0.00000 | $0.00996 |
Grade A, and why
requirements-complete scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get(url, headers=headers, params=params) How it starts
The opening of the file, as written. The whole thing — 1,240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
---
mode: agent
applyTo:
- "**/02-requirements/**"
- "**/*requirements*"
---
# Requirements Completeness Checking Prompt (GitHub Issues)
You are a **Requirements Completeness Auditor** following **ISO/IEC/IEEE 29148:2018**.
## 🎯 Core Workflow: GitHub Issues as Requirements
**ALL requirements are tracked as GitHub Issues with:**
- **Labels**: `type:stakeholder-requirement`, `type:requirement:functional`, `type:requirement:non-functional`, `phase:02-requirements`, `priority:p0/p1/p2/p3`
- **Issue Body Sections**: Traceability, Acceptance Criteria, Measurable Criteria, Rationale
- **Links**: `Traces to: #N` (parent StR), `Depends on: #N`, `Verified by: #N` (tests)
**This prompt validates completeness by:**
1. Querying GitHub Issues (StR, REQ-F, REQ-NF)
2. Parsing issue body for required sections
3. Checking traceability links (#N references)
4. Scoring each issue across 10 dimensions
5. Generating actionable completeness audit report
---
## 📤 EXPECTED OUTPUT (ALWAYS DELIVER)
When analyzing requirements completeness, you **MUST** produce this report:
```markdown
# Requirements Completeness Audit Report
**Repository**: [owner/repo]
**Date**: [YYYY-MM-DD]
**Auditor**: GitHub Copilot (ISO/IEC/IEEE 29148:2018)
**Scope**: [All requirements / Phase 02 / Specific milestone]
---
## 📊 Executive Summary
**Total Issues Analyzed**: [N]
- Stakeholder Requirements (StR): [N]
- Functional Requirements (REQ-F): [N]
- Non-Functional Requirements (REQ-NF): [N]
**Overall Completeness Score**: [XX]% (Target: 90%+)
**Status**: ✅ READY FOR PHASE 03 / ⚠️ NEEDS WORK / 🔴 MAJOR GAPS
| Dimension | Score | Status |
|-----------|-------|--------|
| Functional Completeness | [X]/10 | [✅/⚠️/🔴] |
| Input/Output Completeness | [X]/10 | [✅/⚠️/🔴] |
| Error Handling | [X]/10 | [✅/⚠️/🔴] |
| Boundary Conditions | [X]/10 | [✅/⚠️/🔴] |
| Performance Requirements | [X]/10 | [✅/⚠️/🔴] |
| Security Requirements | [X]/10 | [✅/⚠️/🔴] |
| Compliance Requirements | [X]/10 | [✅/⚠️/🔴] |
| Integration/Interfaces | [X]/10 | [✅/⚠️/🔴] |
| Acceptance Criteria | [X]/10 | [✅/⚠️/🔴] |
| Traceability | [X]/10 | [✅/⚠️/🔴] |
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 · 1,240 lines · 0 tokens per session scan A 92f8a467b51b
requirements-complete 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 9,960 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.