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/instructions/phase-08-transition.instructions.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/instructions/zarfld/presonus-studiolive-mcp/phase-08-transition)<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-08-transition"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-08-transition/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/instructions/zarfld/presonus-studiolive-mcp/phase-08-transition"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-08-transition.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.03824 | $0.03824 |
| Opus 5.5 | $0.01530 | $0.01530 |
| Sonnet 5.5 | $0.00765 | $0.00765 |
| Haiku 4.5 | $0.00382 | $0.00382 |
Grade A, and why
presonus-studiolive-mcp phase-08-transition.instructions.md scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://api.example.com/health How it starts
The opening of the file, as written. The whole thing — 602 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 08: Transition (Deployment)
Standards: ISO/IEC/IEEE 12207:2017 (Transition Process)
XP Integration: Small Releases, Continuous Deployment
🎯 Phase Objectives
- Deploy system to production environment
- Train users and operators
- Provide user documentation
- Establish support processes
- Conduct operational readiness review
- Transition system to operations team
📋 Deployment Tracking via GitHub
Release Issues
Create a release issue for each deployment:
Title: Release v1.2.0 - User Authentication Feature
Features Deployed:
- #45 (REQ-F-AUTH-001: User Login) ✅
- #46 (REQ-NF-SECU-002: Session Security) ✅
- #79 (ARC-C-AUTH: Auth Service) ✅
Deployment Checklist:
- All tests passing (100%)
- Security scan completed
- Performance benchmarks met
- Database migrations tested
- Rollback plan documented
- Monitoring dashboards configured
- Documentation updated
- Training materials prepared
- Operations team notified
- Deploy to staging ✅
- Staging smoke tests ✅
- Deploy to production
- Production smoke tests
- Monitor for 24 hours
Verified by:
- #120, #121, #122 (TEST issues)
Documentation:
- User Guide: [link]
- API Docs: [link]
- Runbook: [link]
Closing Implemented Requirements
After successful deployment:
-
Update requirement issues with deployment info:
## Deployment Status ✅ Deployed: v1.2.0 on 2025-11-12 Environment: Production Release: #150 -
Close implemented issues using release PR:
git commit -m "Release v1.2.0 Closes #45, #46 Release: #150" -
Update stakeholder issues with completion status
📋 ISO/IEC/IEEE 12207:2017 Compliance
Transition Process Activities
-
Transition Planning (tracked via release issues)
- Define deployment strategy
- Identify training needs
- Plan documentation
- Establish support structure
-
Deployment (tracked via release issue checklist)
- Deploy to production
- Verify deployment (smoke tests)
- Conduct smoke tests
- Monitor initial operation
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 · 602 lines · 3,824 tokens per session scan A 7c72a1d4107d
presonus-studiolive-mcp phase-08-transition.instructions.md is an instructions file published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 3,824 tokens to every session, about $0.0153 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.