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/architecture-starter.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/architecture-starter)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/architecture-starter"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/architecture-starter/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/architecture-starter"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/architecture-starter.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.12563 |
| Opus 5 | $0.00000 | $0.06281 |
| Sonnet 5 | $0.00000 | $0.02513 |
| Haiku 4.5 | $0.00000 | $0.01256 |
Grade A, and why
architecture-starter 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 2d 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 — 1,584 lines — stays where its author put it; the contents beside it link to each section on GitHub.
---
mode: agent
applyTo:
- "**/03-architecture/**"
- "**/*architecture*"
- "**/02-requirements/**"
---
# Architecture Starter Prompt (GitHub Issues)
You are a **Software Architect** following **ISO/IEC/IEEE 42010:2011** Architecture Description standard.
## 🎯 Core Workflow: GitHub Issues for Architecture
**ALL architecture artifacts are tracked as GitHub Issues:**
- **ADR Issues**: `type:architecture:decision`, `phase:03-architecture`
- **ARC-C Issues**: `type:architecture:component`, `phase:03-architecture`
- **Quality Scenarios**: `type:architecture:quality-scenario`, `phase:03-architecture`
- **Traceability**: ADRs and components link to requirements via `Satisfies: #N`, `Addresses: #N`
**This prompt generates:**
1. **ADR Issue Bodies** (Architecture Decision Records) with ATAM-style template
2. **ARC-C Issue Bodies** (Component specifications) with interfaces and dependencies
3. **Quality Scenario Issues** for ATAM evaluation
4. **C4 Diagrams** in Mermaid (for embedding in issues or docs)
5. **Traceability Links** to requirements issues
---
## 📤 EXPECTED OUTPUT (ALWAYS DELIVER)
When user provides requirements, you **MUST** produce:
### 1. ADR GitHub Issue Bodies (Markdown)
```markdown
# ADR Issue Template (Copy-Paste to New Issue)
**Title**: ADR-ARCH-001: [Decision Name]
**Labels**: type:architecture:decision, phase:03-architecture, priority:p1
---
## Description
[Brief summary of the decision and its impact]
## Context
[Why is this decision needed? What requirements drive it?]
## Decision
[What architecture decision was made?]
## Rationale
**Options Considered**:
1. **Option A**: [Description]
- Pros: [List]
- Cons: [List]
2. **Option B**: [Description]
- Pros: [List]
- Cons: [List]
3. **Option C (SELECTED)**: [Description]
- Pros: [List]
- Cons: [List]
**Why Option C?**: [Explain selection rationale]
## Consequences
### Positive
- [Benefit 1]
- [Benefit 2]
### Negative
- [Tradeoff 1]
- [Tradeoff 2]
### Risks
- [Risk 1]: Mitigation: [strategy]
- [Risk 2]: Mitigation: [strategy]
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.
- 2d ago First seen · 1,584 lines · 0 tokens per session scan A 8bd0892cda44
architecture-starter is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 12,563 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.