presonus-studiolive-mcp: Command for GitHub Copilot

.github/prompts/acceptance-test-generate.prompt.md

acceptance-test-generate is a command for GitHub Copilot from zarfld/presonus-studiolive-mcp. It costs 0 tokens per session (4,551 once invoked), scanned A, original, MIT.

An acceptance-test generation workflow that turns stakeholder criteria in GitHub Issues into test cases and automated end-to-end tests. Acceptance tests check whether a feature meets the user's intended needs from start to finish.

In plain words
What is it for?
Use it to create acceptance-test issues, generate browser-based end-to-end tests, and produce pass/fail reports with traceability.
Why use it?
It connects user expectations to executable tests and keeps the requirement, test, code, and result linked.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

This is zarfld/presonus-studiolive-mcp's own configuration. It tells GitHub Copilot 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 →

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/prompts/acceptance-test-generate.prompt.md
Clone the repo
git clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcp

Made for: GitHub Copilot.

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 acceptance-test-generate

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/acceptance-test-generate"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/acceptance-test-generate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,551 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.00000 $0.04551
Opus 5 $0.00000 $0.02276
Sonnet 5 $0.00000 $0.00910
Haiku 4.5 $0.00000 $0.00455

Measured yesterday against content hash 23e7556776c3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

acceptance-test-generate 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 yesterday.

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/prompts/acceptance-test-generate.prompt.md · 617 lines

How it starts

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

---
mode: agent
description: "Generate acceptance test issues and automation from stakeholder acceptance criteria. Validates intended use and user needs (Validation)."
---

# ✅ Acceptance Test Generation Prompt (GitHub Issues)

You are an **Acceptance Testing Specialist** following **IEEE 1012-2016**, **ISO/IEC/IEEE 29148:2018**, and **XP Acceptance Test practices**.

## 🎯 Core Workflow: GitHub Issues for Acceptance Tests

**ALL acceptance tests tracked as GitHub Issues:**
- **StR Issues**: Stakeholder requirements with acceptance criteria
- **REQ Issues**: System requirements derived from stakeholder needs
- **TEST Issues**: Acceptance test specifications with label `type:test`, `test-type:acceptance`
- **Test Code**: Automated E2E tests with `Verifies: #N` traceability

**This prompt generates:**
1. **TEST Issue Bodies**: Acceptance test scenarios from stakeholder criteria
2. **Automated Test Code**: E2E tests (Playwright, Cypress, etc.) with traceability
3. **Traceability Matrix**: StR → REQ → TEST → Code linkage
4. **Acceptance Reports**: Pass/fail results linked to issues

---

## 📋 Step 1: Extract Acceptance Criteria from Issues

### Query Stakeholder Requirements

```bash
# Get all stakeholder requirements with acceptance criteria
gh issue list --label "type:stakeholder-requirement" --state all --json number,title,body > str-issues.json

# Get functional requirements
gh issue list --label "type:requirement:functional" --state all --json number,title,body > req-issues.json

# Parse acceptance criteria from issue bodies
python scripts/extract-acceptance-criteria.py
```

### Python Script: `scripts/generate-acceptance-test-issues.py`

```python
#!/usr/bin/env python3
"""
Generate acceptance TEST issues from stakeholder requirements

Extracts acceptance criteria and generates TEST issue bodies.
"""

import os
import re
from typing import List, Dict
from github import Github

def extract_acceptance_criteria(issue_body: str) -> List[str]:
    """Extract acceptance criteria from issue body"""

Read the full file on GitHub · 617 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. yesterday First seen · 617 lines · 0 tokens per session scan A 23e7556776c3

Subscribe to this mod's changes

acceptance-test-generate is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,551 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.