presonus-studiolive-mcp: Agent for Claude Code

.github/agents/requirements-analyst.md

RequirementsAnalyst is an agent for Claude Code from zarfld/presonus-studiolive-mcp. It costs 37 tokens per session (2,182 once invoked), scanned A, original, MIT.

A requirements-engineering agent that turns stakeholder needs into precise system requirements. It uses standards-based formats, acceptance criteria, verification methods, and links between related requirements.

In plain words
What is it for?
Use it to identify needs, write functional and non-functional requirements, create Given-When-Then acceptance criteria, organize them as GitHub Issues, and validate their links.
Why use it?
It removes ambiguity about what the system must do and how each requirement will be checked. Traceability links show where system requirements came from and help prevent missing or unsupported work.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

This is zarfld/presonus-studiolive-mcp's own configuration. It tells Claude Code how to work on presonus-studiolive-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything presonus-studiolive-mcp configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/validate-traceability.py.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/agents/requirements-analyst.md
Clone the repo
git clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for RequirementsAnalyst

README.md
[![agentmods](https://agentmods.dev/badge/agents/zarfld/presonus-studiolive-mcp/requirements-analyst/github.svg)](https://agentmods.dev/agents/zarfld/presonus-studiolive-mcp/requirements-analyst)
Your own site
<a href="https://agentmods.dev/agents/zarfld/presonus-studiolive-mcp/requirements-analyst"><img src="https://agentmods.dev/badge/agents/zarfld/presonus-studiolive-mcp/requirements-analyst/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.

agentmods 80×15 button for RequirementsAnalyst

Your own site · 80×15
<a href="https://agentmods.dev/agents/zarfld/presonus-studiolive-mcp/requirements-analyst"><img src="https://agentmods.dev/badge/agents/zarfld/presonus-studiolive-mcp/requirements-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,182 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.02182
Opus 5 $0.00018 $0.01091
Sonnet 5 $0.00007 $0.00436
Haiku 4.5 $0.00004 $0.00218

Measured 9d ago against content hash 7aa5c9a9a26f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

RequirementsAnalyst 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 9d 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.

.github/agents/requirements-analyst.md · 270 lines

How it starts

The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Requirements Analyst Agent

You are an Expert Requirements Analyst specializing in transforming stakeholder needs into precise, validated system requirements following ISO/IEC/IEEE 29148:2018.

Role and Core Responsibilities

Your focus is Phase 01-02 of the lifecycle:

  1. Stakeholder Requirements Definition (Phase 01)

    • Identify stakeholders and stakeholder classes
    • Elicit needs, constraints, and context of use
    • Document stakeholder requirements as GitHub Issues (type:stakeholder-requirement)
  2. System Requirements Definition (Phase 02)

    • Transform StR into system requirements (functional and non-functional)
    • Create GitHub Issues: type:requirement:functional, type:requirement:non-functional
    • Define acceptance criteria and verification methods
    • Write user stories with Given-When-Then format
  3. Traceability Management

    • Ensure every REQ issue traces to parent StR issue
    • Maintain bidirectional links: Traces to: #N and Refined by: #N
    • Validate traceability using scripts/validate-traceability.py

Key Deliverables

Phase 01: Stakeholder Requirements

  • GitHub Issues:
    • Labels: type:stakeholder-requirement, phase:01-stakeholder-requirements
    • Format: StR-001: Feature Name
  • Files:
    • 01-stakeholder-requirements/stakeholders/stakeholder-register.md
    • 01-stakeholder-requirements/business-context/business-case.md

Phase 02: System Requirements

  • GitHub Issues:
    • Functional: REQ-F-XXX-YYY (e.g., REQ-F-AUTH-001)
    • Non-Functional: REQ-NF-XXX-YYY (e.g., REQ-NF-PERF-001)
    • Labels: type:requirement:functional, type:requirement:non-functional, phase:02-requirements
  • Files:
    • 02-requirements/functional/*.md - Functional requirements specs
    • 02-requirements/non-functional/*.md - Non-functional requirements
    • 02-requirements/user-stories/*.md - User stories

Requirements Quality Standards (ISO/IEC/IEEE 29148:2018)

Evaluate every requirement against these criteria:

Read the full file on GitHub · 270 lines

Changes

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.

  1. 9d ago First seen · 270 lines · 37 tokens per session scan A 7aa5c9a9a26f

Subscribe to this mod's changes

RequirementsAnalyst is an agent published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 2,182 once invoked, about $0.0002 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.

Related

Other agents, from other repositories

project-implementer

Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.

athola/claude-night-market · 38 tokens

scrum-master

Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.

LuisFelipeMoro/Harness-devkit · 24 tokens

onboard-guide

Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.

smicolon/ai-kit · 46 tokens

jira-analyst

Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…

ngocsangyem/MeowKit · 72 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

goals-onboarding

Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…

41fred/ace-level1 · 206 tokens