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-03-architecture.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-03-architecture)<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-03-architecture"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-03-architecture/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-03-architecture"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-03-architecture.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.07173 | $0.07173 |
| Opus 5 | $0.03587 | $0.03587 |
| Sonnet 5 | $0.01435 | $0.01435 |
| Haiku 4.5 | $0.00717 | $0.00717 |
Grade A, and why
presonus-studiolive-mcp phase-03-architecture.instructions.md 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 993 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 03: Architecture Design
Standards: ISO/IEC/IEEE 42010:2011 (Architecture Description), IEEE 1016-2009
XP Integration: Simple Design, Metaphor, Refactoring Foundation
🎯 Phase Objectives
- Define system architecture and structure
- Create architectural views for different stakeholder concerns
- Document architectural decisions (ADRs)
- Identify architectural patterns and styles
- Define component boundaries and interfaces
- Establish technical foundation for detailed design
📋 Architecture Documentation Approach
⭐ PRIMARY: GitHub Issues (Recommended)
Architecture artifacts should be captured as GitHub Issues using ADR (Architecture Decision Record) and ARC-C (Architecture Component) templates.
Creating Architecture Decisions as GitHub Issues
-
Navigate to Issues → New Issue
-
Select Template: "Architecture Decision (ADR)"
-
Complete Required Fields:
- Title: Decision statement (e.g., "Use PostgreSQL for persistent data storage")
- Requirements Addressed: Link to parent REQ issues using
#Nsyntax - Context: What forces are influencing this decision
- Decision: What architecture decision was made
- Alternatives Considered: Other options evaluated
- Consequences: Positive and negative impacts
- Status: Proposed / Accepted / Deprecated / Superseded
-
Apply Labels:
architecture-decisionphase-03- Category labels (e.g.,
security,performance,scalability)
-
Submit → GitHub assigns issue number (e.g., #78)
-
Set Status in GitHub Project (see Status Management Guide):
- Initial Status: "Proposed"
- Progression: Proposed → Under Review → Accepted/Rejected → Close
- Close When: Decision finalized with rationale documented
Creating Architecture Components as GitHub Issues
- Navigate to Issues → New Issue
- Select Template: "Architecture Component (ARC-C)"
- Complete Required Fields:
- Title: Component name (e.g., "User Authentication Service")
- Architecture Decisions: Link to related ADR issues
- Component Purpose: Responsibility and scope
- Interfaces: APIs, events, data contracts
- Dependencies: Other components/services
- Technology Stack: Languages, frameworks, tools
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.
- 12d ago First seen · 993 lines · 7,173 tokens per session scan A 3fc8f8e79bc1
presonus-studiolive-mcp phase-03-architecture.instructions.md is an instructions file published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 7,173 tokens to every session, about $0.0359 per session on Opus 5. 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-08-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).