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-02-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-02-requirements)<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-02-requirements"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-02-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-02-requirements"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-02-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.05601 | $0.05601 |
| Opus 5 | $0.02801 | $0.02801 |
| Sonnet 5 | $0.01120 | $0.01120 |
| Haiku 4.5 | $0.00560 | $0.00560 |
Grade A, and why
presonus-studiolive-mcp phase-02-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 — 707 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 02: Requirements Analysis & Specification
Standards: ISO/IEC/IEEE 29148:2018 (System Requirements), ISO/IEC/IEEE 12207:2017
XP Integration: User Stories, Acceptance Tests, YAGNI Principle
🎯 Phase Objectives
- Transform stakeholder requirements into system requirements
- Define functional and non-functional requirements
- Create detailed use cases and user stories
- Establish requirements traceability
- Define testable acceptance criteria
📋 Requirements Capture Method
GitHub Issues (Primary and Recommended)
All requirements MUST be captured as GitHub Issues using the Functional Requirement (REQ-F) or Non-Functional Requirement (REQ-NF) templates.
Benefits:
- ✅ No YAML front matter required - metadata captured via issue fields, labels, and project columns
- ✅ Traceability via
#Nsyntax in issue bodies - ✅ ISO/IEC/IEEE 29148:2018 compliance via issue templates
- ✅ Automated validation via GitHub Actions
- ✅ Real-time collaboration and discussion
- ✅ Integration with pull requests and CI/CD
- ✅ Searchable and filterable with labels and milestones
📋 ISO/IEC/IEEE 29148:2018 Compliance
System Requirements Process Activities
-
Requirements Analysis
- Decompose stakeholder requirements
- Identify system boundaries
- Define interfaces
- Analyze feasibility
- Resolve conflicts
-
System Requirements Specification
- Define functional requirements
- Define non-functional requirements (quality attributes)
- Specify constraints
- Define interfaces
- Create System Requirements Specification (SyRS)
-
Requirements Validation
- Review for completeness
- Check consistency
- Verify traceability to stakeholder requirements
- Validate with stakeholders
🎨 XP Practices for This Phase
User Stories
Transform requirements into user stories:
As a [user role]
I want to [action/capability]
So that [business value]
Acceptance Criteria:
- Given [context]
- When [action]
- Then [outcome]
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 · 707 lines · 5,601 tokens per session scan A 656ee8f36939
presonus-studiolive-mcp phase-02-requirements.instructions.md is an instructions file published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 5,601 tokens to every session, about $0.0280 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.
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).
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.