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_3to4.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_3to4)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4/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_3to4"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/phase-transition_3to4.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.00603 |
| Opus 5 | $0.00000 | $0.00302 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
phase-transition_3to4 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.
What it actually says
Phase 04: Detailed Design - Standards-Compliant Transition
GitHub Issues Workflow: Update architecture component issues (ARC-C) with detailed design specifications. Add design comments to architecture issues or create supplementary design documentation that references issues. Maintain traceability via issue references: #REQ → #ARC-C → code implementation → #TEST.
Design Documentation: You may create supplementary design markdown files in
04-design/components/, but they MUST reference the canonical GitHub Issues using#Nsyntax:# Component Design: User Authentication **Architecture Issue**: #45 (ARC-C-AUTH-001: Authentication Service) **Requirements**: #23 (REQ-F-AUTH-001), #24 (REQ-NF-SECU-002) ## Component Structure [Detailed design content here...]
Context: I have completed Phase 03 (Architecture Design) following ISO/IEC/IEEE 42010:2011 standards and am ready to transition to Phase 04 (Detailed Design) following IEEE 1016-2009 standards.
Completed Architecture Artifacts:
- Architecture specification with multiple viewpoints (Context, Logical, Deployment)
- Architecture Decision Records (ADRs) documenting key decisions
- All ADRs have rationale and link to requirements
- Quality attribute scenarios (Performance, Availability, Security)
- Architecture evaluation completed
- All architecture components identified with ARC-C-* IDs
- Traceability matrix linking requirements (REQ-) to architecture components (ARC-C-) and ADRs
Phase 04 Objectives (per IEEE 1016-2009):
- Transform architecture components into detailed component designs
- Specify interfaces, data structures, and algorithms
- Create component-level design descriptions
- Maintain traceability: ARC-C-* → DES-C-* → implementation units
- Apply XP Simple Design principles (YAGNI, minimal complexity)
Standards to Apply:
- IEEE 1016-2009: Software Design Descriptions format
- ISO/IEC/IEEE 12207:2017: Design Definition process
- XP Practices: Simple Design, Refactoring readiness, Test-first design
Specific Request (enforce traceability & unique IDs): Please guide me through Phase 04 detailed design activities:
- Review my architecture artifacts for design readiness
- Help create component design specifications using IEEE 1016 format
- Define interfaces and data models with proper traceability
- Prepare test-driven design approach for Phase 05 implementation
- Ensure design decisions support XP practices (especially TDD and refactoring)
Questions for Clarification (Answer before generating design specs):
- Should I prioritize certain architecture components for detailed design first?
- Are there specific performance or complexity constraints I should consider?
- What level of design detail is appropriate for the implementation approach planned?
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.
- 3d ago First seen · 51 lines · 0 tokens per session scan A 3c7ddb159e27
phase-transition_3to4 is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 603 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.