presonus-studiolive-mcp: Command for GitHub Copilot

.github/prompts/phase-transition_4to5.prompt.md

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

A transition command for moving from detailed design into implementation, with links between GitHub Issues, code, pull requests, and tests. TDD, or test-driven development, means using tests as part of the process of defining and checking the code.

In plain words
What is it for?
Use it to guide implementation work, add issue references to code and pull requests, and connect requirements through architecture to verification tests.
Why use it?
It helps preserve a clear record of which requirements and design decisions each implementation and test address.

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/phase-transition_4to5.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 phase-transition_4to5

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/phase-transition_4to5"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/phase-transition_4to5.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 721 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.00721
Opus 5 $0.00000 $0.00360
Sonnet 5 $0.00000 $0.00144
Haiku 4.5 $0.00000 $0.00072

Measured 4d ago against content hash 895d881e6f16, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

phase-transition_4to5 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 4d 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/phase-transition_4to5.prompt.md · 67 lines

What it actually says

Phase 05: Implementation - TDD & Standards-Compliant Development

GitHub Issues Traceability: All code MUST reference implementing GitHub Issues in docstrings and comments. Use Implements: #N, Verifies: #N, Architecture: #N syntax. Traceability path via issues: #REQ-F → #ARC-C → Pull Request (#PR) → #TEST.

Code Documentation Examples:

"""
User authentication service.

Implements: #23 (REQ-F-AUTH-001: User Login)
Architecture: #45 (ARC-C-AUTH-001: Authentication Service)
Verified by: #89 (TEST-AUTH-001: Authentication Tests)

See: https://github.com/org/repo/issues/23
"""
class AuthenticationService:
    pass
/**
 * User login endpoint
 * 
 * @implements #23 REQ-F-AUTH-001: User Login
 * @architecture #45 ARC-C-AUTH-001: Authentication Service
 * @see https://github.com/org/repo/issues/23
 */
export async function loginUser(credentials: Credentials): Promise<User> {
  // Implementation
}

Pull Request Requirements: Every PR MUST link to implementing issue(s) using Fixes #N or Implements #N in PR description.

Context: I have completed Phase 04 (Detailed Design) following IEEE 1016-2009 standards and am ready to transition to Phase 05 (Implementation) following ISO/IEC/IEEE 12207:2017 Implementation Process and XP practices.

Completed Design Artifacts:

  • Component design specifications (DES-C-* IDs)
  • Interface definitions and data structures
  • Algorithm specifications
  • Design traceability: REQ-* → ARC-C-* → DES-C-*

Phase 05 Objectives (per ISO/IEC/IEEE 12207:2017 + XP):

  1. Implement design specifications using Test-Driven Development (TDD)
  2. Write clean, maintainable code following XP Simple Design principles
  3. Maintain continuous integration and frequent commits
  4. Establish traceability: DES-C-* → Implementation units → TEST-*
  5. Apply pair programming and collective code ownership

Standards & Practices to Apply:

  • ISO/IEC/IEEE 12207:2017: Implementation Process
  • XP Core Practices: TDD (Red-Green-Refactor), Simple Design, Continuous Integration
  • Code Quality: Clean code principles, SOLID principles, refactoring

Specific Request (enforce TDD + traceability): Please guide me through Phase 05 implementation activities:

  1. Help establish TDD workflow for my design components
  2. Create implementation structure following design specifications
  3. Write tests first, then minimal code to pass (Red-Green-Refactor)
  4. Ensure proper traceability from design to code to tests
  5. Apply XP Simple Design principles (YAGNI, no duplication, clear intent)

Questions for Clarification (answer before creating code scaffolds):

  • Which design components should I implement first (dependency order)?
  • What testing framework and project structure do you recommend?
  • Are there specific performance or quality constraints for the implementation?
  • Should I set up CI/CD pipeline integration during this phase?
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. 4d ago First seen · 67 lines · 0 tokens per session scan A 895d881e6f16

Subscribe to this mod's changes

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