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/README-IMPROVEMENTS.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/readme-improvements)<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.
<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>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.02237 |
| Opus 5.5 | $0.00000 | $0.00895 |
| Sonnet 5.5 | $0.00000 | $0.00447 |
| Haiku 4.5 | $0.00000 | $0.00224 |
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 1mo 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 — 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
-
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
-
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
-
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
-
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.
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.
- 1mo ago First seen · 358 lines · 0 tokens per session scan A 788a96438799
README-IMPROVEMENTS is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 4d 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.
Other commands, from other repositories
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
data-mesh-contract
Create federated data product contracts for mesh architectures with SLAs, governance, and interoperability guarantees (project).
atrs
Generate Algorithmic Transparency Recording Standard (ATRS) record for AI/algorithmic tools.
fr-rgpd
You are helping an enterprise architect generate a French CNIL Compliance Assessment — the French-specific GDPR layer applied by the CNIL (Commission Nationale de l'Informatique et des Libertés). Run this after /arckit-eu:eu-rgpd to add French obligations that go beyond the EU GDPR baseline.
flow-nexus-neural
Train and deploy neural networks in distributed sandboxes.
performance-bottlenecks
Identify and resolve performance bottlenecks in your development workflow.