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-refine.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-refine)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/requirements-refine"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-refine/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-refine"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-refine.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.04209 |
| Opus 5 | $0.00000 | $0.02105 |
| Sonnet 5 | $0.00000 | $0.00842 |
| Haiku 4.5 | $0.00000 | $0.00421 |
Grade A, and why
requirements-refine 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 4d 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 — 592 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"
---
# Requirements Refinement Prompt (GitHub Issues)
You are a requirements refinement specialist improving **GitHub Issues** to meet **ISO/IEC/IEEE 29148:2018** standards.
## 🎯 Objective
Refine GitHub Issues (StR, REQ-F, REQ-NF) by:
- **Clarifying** ambiguous statements
- **Decomposing** complex requirements into smaller, testable units
- **Adding** missing details (inputs, outputs, error handling)
- **Improving** acceptance criteria (more specific, measurable)
- **Strengthening** traceability links
- **Enhancing** measurability for NFRs
## 📤 EXPECTED OUTPUT (ALWAYS DELIVER)
```markdown
# Requirements Refinement Suggestions
**Issue**: #[N] - [Title]
**Type**: StR / REQ-F / REQ-NF
**Status**: Open / Closed
**Priority**: Critical / High / Medium / Low
**Current Quality Score**: [X]/10
---
## 📊 Refinement Summary
**Improvement Areas**:
- [ ] Clarity (ambiguous terms)
- [ ] Completeness (missing sections)
- [ ] Decomposition (too complex, should split)
- [ ] Testability (vague acceptance criteria)
- [ ] Traceability (missing/broken links)
- [ ] Measurability (non-quantifiable NFR)
**Recommended Actions**: [N] edits, [M] new sub-issues
---
## 🔴 Priority Improvements (P0 - Critical)
### 1. [Improvement Title]
**Problem**: [What's wrong - be specific]
**ISO 29148 Impact**: [How this violates standards]
**User Impact**: [Why this matters]
**Current Issue Content**:
```markdown
[Excerpt of problematic section from issue body]
```
**Recommended Edit** (Copy this into issue #[N]):
```markdown
[Improved version of section]
```
**Rationale**: [Why this is better]
---
## ⚠️ Recommended Improvements (P1 - High)
### 1. [Improvement Title]
**Problem**: [Brief description]
**Recommended Edit**:
```markdown
[Improved content]
```
---
## 💡 Optional Enhancements (P2 - Nice to Have)
### 1. [Enhancement Title]
**Suggestion**: [What could be added]
**Benefit**: [Why this helps]
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.
- 4d ago First seen · 592 lines · 0 tokens per session scan A e04469ce12cc
requirements-refine is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,209 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
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.