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/acceptance-test-generate.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/acceptance-test-generate)<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.
<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>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.04551 |
| Opus 5 | $0.00000 | $0.02276 |
| Sonnet 5 | $0.00000 | $0.00910 |
| Haiku 4.5 | $0.00000 | $0.00455 |
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.
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"""
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.
- yesterday First seen · 617 lines · 0 tokens per session scan A 23e7556776c3
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.
Other commands, from other repositories
playwright-test-heal
Run all my tests and fix the failing ones.
paul:verify
Guide manual user acceptance testing of recently built features.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.