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/instructions/phase-01-stakeholder-requirements.instructions.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/instructions/zarfld/presonus-studiolive-mcp/phase-01-stakeholder-requirements)<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-01-stakeholder-requirements"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-01-stakeholder-requirements/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/instructions/zarfld/presonus-studiolive-mcp/phase-01-stakeholder-requirements"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-01-stakeholder-requirements.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.03666 | $0.03666 |
| Opus 5 | $0.01833 | $0.01833 |
| Sonnet 5 | $0.00733 | $0.00733 |
| Haiku 4.5 | $0.00367 | $0.00367 |
Grade A, and why
presonus-studiolive-mcp phase-01-stakeholder-requirements.instructions.md 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 10d 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 — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 01: Stakeholder Requirements Definition
Standards: ISO/IEC/IEEE 29148:2018 (Stakeholder Requirements), ISO/IEC/IEEE 12207:2017
XP Integration: Planning Game, Customer Involvement, User Stories Foundation
🎯 Phase Objectives
- Identify and document all stakeholders and their concerns
- Elicit stakeholder needs and expectations
- Define business context and constraints
- Establish success criteria and acceptance measures
- Create foundation for system requirements
📋 ISO/IEC/IEEE 29148:2018 Compliance
Stakeholder Requirements Process Activities
-
Stakeholder Identification
- Define all stakeholder classes
- Identify representatives from each class
- Document stakeholder roles and responsibilities
- Map stakeholder concerns and interests
-
Requirements Elicitation
- Conduct stakeholder interviews
- Facilitate workshops and brainstorming sessions
- Review existing documentation
- Analyze competitor solutions
- Document user pain points and needs
-
Requirements Analysis
- Identify conflicting requirements
- Prioritize stakeholder needs
- Analyze feasibility and constraints
- Define acceptance criteria
-
Requirements Documentation
- Create Stakeholder Requirements Specification (StRS)
- Document business context
- Define scope and boundaries
- Document assumptions and constraints
🎨 XP Practices for This Phase
Planning Game
- Exploration Phase: Understand business value
- Commitment Phase: Establish iteration scope
- Steering Phase: Track progress and adjust
Customer Involvement
- Embed customer representative in team
- Daily customer feedback
- Customer-defined acceptance tests
- Customer prioritization of features
User Story Foundation
Start capturing requirements as user stories:
As a [stakeholder role]
I want [goal/desire]
So that [benefit/value]
📝 Requirements Documentation Approach
⭐ PRIMARY: GitHub Issues (Recommended)
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.
- 10d ago First seen · 457 lines · 3,666 tokens per session scan A ffe4d50992b2
presonus-studiolive-mcp phase-01-stakeholder-requirements.instructions.md is an instructions file published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed today), licensed MIT. It adds 3,666 tokens to every session, about $0.0183 per session on Opus 5. 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-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).