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/phase-transition_4to5.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/phase-transition_4to5)<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.
<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>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.00721 |
| Opus 5 | $0.00000 | $0.00360 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
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.
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: #Nsyntax. 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 #NorImplements #Nin 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):
- Implement design specifications using Test-Driven Development (TDD)
- Write clean, maintainable code following XP Simple Design principles
- Maintain continuous integration and frequent commits
- Establish traceability: DES-C-* → Implementation units → TEST-*
- 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:
- Help establish TDD workflow for my design components
- Create implementation structure following design specifications
- Write tests first, then minimal code to pass (Red-Green-Refactor)
- Ensure proper traceability from design to code to tests
- 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?
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.
- 4d ago First seen · 67 lines · 0 tokens per session scan A 895d881e6f16
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.
Other commands, from other repositories
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
build
Implement the next task incrementally — build, test, verify, commit.
conductor-implement
Execute tasks from track plan with TDD workflow and git commits.