presonus-studiolive-mcp: Command for GitHub Copilot

.github/prompts/README-IMPROVEMENTS.md

README-IMPROVEMENTS is a command for GitHub Copilot from zarfld/presonus-studiolive-mcp. It costs 0 tokens per session (2,237 once invoked), scanned A, original, MIT.

A set of improvements to requirements prompts that adds clear output formats, step-by-step workflows, and complete templates. It is documentation about how coding agents should produce project deliverables.

In plain words
What is it for?
Use it to make requirements prompts easier for agents to follow and more likely to produce the expected documents or artifacts.
Why use it?
It addresses incomplete or inconsistent agent responses caused by buried templates, unclear sequences, and missing delivery instructions.

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 →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Test: "Validate all requirements in ./02-requirements/".

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/README-IMPROVEMENTS.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 README-IMPROVEMENTS

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/readme-improvements"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/readme-improvements.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 2,237 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.02237
Opus 5 $0.00000 $0.01118
Sonnet 5 $0.00000 $0.00447
Haiku 4.5 $0.00000 $0.00224

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

Security

Grade A, and why

README-IMPROVEMENTS 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 3d 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/prompts/README-IMPROVEMENTS.md · 358 lines

How it starts

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

Requirements Prompts Improvements

Date: November 6, 2025
Issue: Copilot not consistently delivering expected outputs when executing requirements prompts
Solution: Added explicit "Expected Output" sections with complete templates


🔍 Root Cause Analysis

Problems Identified

  1. No Clear Output Format at Top

    • Deliverable templates were buried deep in the prompt
    • Copilot had to read extensive guidance before understanding what to produce
    • Result: Sometimes stopped after questions, didn't generate final output
  2. Unclear Workflow

    • Missing "START HERE → DO THIS → DELIVER THAT" structure
    • No explicit steps showing what to do when
    • Result: Copilot unclear about sequence of actions
  3. Example-Heavy Content

    • Many examples but unclear which was the actual deliverable
    • Guidance overwhelmed the task definition
    • Result: Copilot focused on examples rather than producing output
  4. Missing Explicit Instructions

    • No "ALWAYS DELIVER" or "MUST PRODUCE" language
    • Lacked emphasis on completing the full deliverable
    • Result: Partial outputs or summaries instead of complete documents

✅ Solutions Implemented

1. Added "📤 EXPECTED OUTPUT" Section

Location: Immediately after the agent role definition (lines 10-80 typically)

Format:

## 📤 EXPECTED OUTPUT (ALWAYS DELIVER)

When [trigger condition], you **MUST** produce:

[Complete template showing exactly what to generate]

Benefits:

  • ✅ Copilot sees expected output format first
  • ✅ Clear template to follow
  • ✅ No ambiguity about deliverables

2. Added "🎯 Your Task" Section

Location: After expected output, before detailed guidance

Format:

## 🎯 Your Task

When [condition], you will:

**STEP 1**: [Action with reference to output]
**STEP 2**: [Action]
**STEP 3**: [Action]
**STEP 4**: Generate complete [deliverable] (see Expected Output above)

**Always deliver [output type]!** Do not skip or summarize.

Read the full file on GitHub · 358 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. 3d ago First seen · 358 lines · 0 tokens per session scan A 788a96438799

Subscribe to this mod's changes

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