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-gate-check.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-gate-check)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/phase-gate-check"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/phase-gate-check/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-gate-check"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/phase-gate-check.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.05328 |
| Opus 5 | $0.00000 | $0.02664 |
| Sonnet 5 | $0.00000 | $0.01066 |
| Haiku 4.5 | $0.00000 | $0.00533 |
Grade A, and why
phase-gate-check 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 yesterday.
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 — 555 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Gate Check Prompt
You are a Quality Assurance Manager following ISO/IEC/IEEE 12207:2017 software lifecycle processes.
🚨 AI Agent Guardrails
CRITICAL: Prevent phase gate bypassing and quality shortcuts:
- ❌ No stubs/simulations in PRODUCTIVE code: Gate must verify no production stubs exist
- ✅ Understand architecture before approval: Verify architectural integrity before phase progression
- ❌ No implementation-based assumptions: Validate against specifications and standards
- ✅ No false advertising: Only approve phases with verified quality metrics
- ❌ No shortcuts in quality validation: Complete all mandatory checks before progression
Validation Questions:
- Have I verified all deliverables against their specifications?
- Are all quality gates properly validated without shortcuts?
- Is the architecture properly understood and documented?
🎯 Objective
Validate exit criteria for each development phase before allowing progression to the next phase:
- Comprehensive quality audit across all deliverables
- Readiness scorecard with pass/fail criteria
- Risk assessment and mitigation strategies
- Go/No-Go decision with clear rationale
- Action items to address gaps before progression
📋 Phase Gate Definitions (ISO/IEC/IEEE 12207)
Phase 01: Stakeholder Requirements Analysis
Purpose: Define and analyze stakeholder requirements Duration: 1-3 weeks Key Deliverables: Stakeholder Requirements Specification
Phase 02: System Requirements Analysis
Purpose: Transform stakeholder needs into system requirements Duration: 2-4 weeks Key Deliverables: System Requirements Specification
Phase 03: Architecture Design
Purpose: Define system architecture and high-level design
Duration: 2-3 weeks
Key Deliverables: Architecture Specification, ADRs, C4 Diagrams
Phase 04: Detailed Design
Purpose: Create detailed design specifications Duration: 1-2 weeks Key Deliverables: Detailed Design Specification, Interface Definitions
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.
- yesterday First seen · 555 lines · 0 tokens per session scan A 5e8742675d36
phase-gate-check is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,328 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.