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/submodules.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/submodules)<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/submodules"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/submodules/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/submodules"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/submodules.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.02420 | $0.02420 |
| Opus 5.5 | $0.00968 | $0.00968 |
| Sonnet 5.5 | $0.00484 | $0.00484 |
| Haiku 4.5 | $0.00242 | $0.00242 |
Grade A, and why
presonus-studiolive-mcp submodules.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 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.
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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submodules and External Modules: Standards-Compliant Guidance
Standards: ISO/IEC/IEEE 12207:2017 (Configuration & Integration), ISO/IEC/IEEE 42010:2011 (Architecture), ISO/IEC/IEEE 29148:2018 (Requirements) XP Integration: Continuous Integration (CI), Collective Ownership, Simple Design, Refactoring
🎯 Objectives
- Enable modular development with clear boundaries (high cohesion, low coupling)
- Support safe reuse while avoiding lock‑step releases and fragile dependencies
- Provide operational rules for adding, updating, and removing submodules (.gitmodules and external folders)
- Maintain traceability, CI predictability, and reproducible builds
📦 Scope and Definitions
- Submodule: A Git repository embedded in another repo, referenced by commit via
.gitmodules. - External module (vendor/third‑party): Code brought in as a subtree, package, or nested folder without a Git link.
- Bounded Context / Module: A coherent unit that encapsulates its model and contracts; may be implemented as its own repo.
- Shared Kernel: A small, intentionally curated subset of shared model agreed by teams with explicit governance.
- Adapter Layer: Translation layer isolating consumers from a provider’s internal model or API changes.
✅ Always Do (Best Practices)
| Practice | Details and Rationale |
|---|---|
| Integrate continuously and frequently | Merge small, frequent changes; never let work sit unintegrated for > a few hours. Run all tests before integration. |
| Maintain cohesion and decoupling | Keep modules cohesive to a single purpose; minimize cross‑module dependencies; prefer narrow, explicit interfaces. |
| Run all tests before integrating | CI must execute all unit/integration tests for the whole system; merges must be green. |
| Align repo structure with ownership | Prefer one repo + one CI build per independently deployable module/microservice. |
| Encapsulate implementation details | Expose only the contract (API/schema); hide internal structures to allow independent evolution. |
| Define meaningful modules | Boundaries reflect domain concepts and ubiquitous language; refactor boundaries as understanding evolves. |
| Refactor module boundaries | Expect change; split/merge modules when cohesion/coupling data suggests it. |
| Use version control for everything | Source, docs, build, and release artifacts are tracked; .gitmodules is reviewed like code. |
| Pin submodule commits | Reference immutable SHAs (not branches) for reproducible builds; document intended compatibility. |
| Add an adapter layer | Decouple your domain from external module APIs; make upgrades local to adapters. |
| Document contracts | Version API/Schema; record breaking changes and migration steps in CHANGELOG/ADR. |
| Automate updates | Provide scripts or CI jobs to update, validate, and test submodule bumps consistently. |
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 · 235 lines · 2,420 tokens per session scan A c6166cd1f6b6
presonus-studiolive-mcp submodules.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 2,420 tokens to every session, about $0.0097 per session on Opus 5.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
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.