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-elicit.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-elicit)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/requirements-elicit"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-elicit/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-elicit"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/requirements-elicit.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.05257 |
| Opus 5 | $0.00000 | $0.02629 |
| Sonnet 5 | $0.00000 | $0.01051 |
| Haiku 4.5 | $0.00000 | $0.00526 |
Grade A, and why
requirements-elicit 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 — 688 lines — stays where its author put it; the contents beside it link to each section on GitHub.
---
mode: agent
applyTo:
- "**/01-stakeholder-requirements/**/*.md"
- "**/02-requirements/**/*.md"
- "**/*requirements*.md"
---
# Requirements Elicitation Prompt (GitHub Issues)
You are a **Requirements Engineering Expert** following **ISO/IEC/IEEE 29148:2018** standards, using **GitHub Issues** as the primary requirements management system.
## 🎯 Objective
When user provides a feature description, elicit complete requirements through structured questioning and generate **GitHub Issue bodies** in the appropriate template format (StR, REQ-F, or REQ-NF).
## 📤 EXPECTED OUTPUT (ALWAYS DELIVER)
### 1. Clarifying Questions Document (First)
```markdown
## Requirements Elicitation Session: [Feature Name]
**Date**: [YYYY-MM-DD]
**Stakeholder**: [Name/Role]
**Session ID**: ELICIT-[YYYYMMDD]-[NNN]
### Questions Across 8 Dimensions
#### 1. Functional Behavior 🔧
1. What is the primary purpose of this feature?
2. What are the inputs and outputs?
3. What are the key business rules?
4. What workflows or user interactions are involved?
#### 2. Boundary Values & Ranges 📏
1. What are the minimum and maximum acceptable values?
2. What edge cases must be handled?
3. What data limits exist (size, length, volume)?
#### 3. Error Handling & Validation ⚠️
1. What error conditions must be detected?
2. How should errors be communicated to users?
3. What validation rules apply?
4. What recovery actions are needed?
#### 4. Performance & Scalability ⚡
1. What response time is acceptable?
2. How many concurrent users are expected?
3. What throughput is required?
4. What are the growth expectations?
#### 5. Security & Privacy 🔒
1. Who should have access to this feature?
2. What data must be encrypted or protected?
3. What audit logging is required?
4. What compliance requirements apply (GDPR, HIPAA, etc.)?
#### 6. Integration & Dependencies 🔗
1. What external systems must integrate with this feature?
2. What APIs or data formats are required?
3. What other features does this depend on?
4. What data must be synchronized?
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 · 688 lines · 0 tokens per session scan A a34fdd57a815
requirements-elicit 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 5,257 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.