presonus-studiolive-mcp: Command for GitHub Copilot

.github/prompts/lint.prompt.md

lint is a command for GitHub Copilot from zarfld/presonus-studiolive-mcp. It costs 0 tokens per session (2,081 once invoked), scanned A, original, MIT.

A linting workflow for GitHub Issue bodies and supporting Markdown documentation. It checks whether requirements and instructions are clear, concise, consistent, and easy for coding agents to follow.

In plain words
What is it for?
Use it to improve requirement wording, standardize issue structure, and ensure supporting documents link back to their canonical GitHub Issues.
Why use it?
It removes ambiguity and repetition from project instructions, reducing misunderstandings during implementation.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

This is zarfld/presonus-studiolive-mcp's own configuration. It tells GitHub Copilot how to work on presonus-studiolive-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything presonus-studiolive-mcp configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/prompts/lint.prompt.md
Clone the repo
git clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcp

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for lint

README.md
[![agentmods](https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/lint/github.svg)](https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/lint)
Your own site
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/lint"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/lint/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.

agentmods 80×15 button for lint

Your own site · 80×15
<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/lint"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,081 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02081
Opus 5 $0.00000 $0.01040
Sonnet 5 $0.00000 $0.00416
Haiku 4.5 $0.00000 $0.00208

Measured yesterday against content hash c7dc0b7e6b88, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

lint 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.

.github/prompts/lint.prompt.md · 350 lines

How it starts

The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Specification Linting and Optimization

⚠️ NOTE: This template now uses GitHub Issues as the single source of truth for requirements, architecture, and tests. This prompt can still be used to lint supplementary documentation files, but the primary artifacts are now GitHub Issue bodies.

Primary Use: Lint GitHub Issue bodies and supplementary markdown documentation Deprecated Use: Linting file-based specification files as primary artifacts

For GitHub Issues workflow, see:

  • Root instructions: .github/copilot-instructions.md (Issue-Driven Development section)
  • Phase instructions: .github/instructions/phase-NN-*.instructions.md

Optimize GitHub Issue bodies and supplementary documentation for clarity, conciseness, and AI coding agent comprehension.

Objectives

  • Clarity: Make issue bodies and documentation unambiguous and easy to understand
  • Conciseness: Remove redundancy while preserving all important details
  • Consistency: Standardize terminology and structure across issues and docs
  • AI-Friendliness: Optimize for GitHub Copilot and other AI coding agents
  • Traceability: Ensure supplementary docs reference canonical GitHub Issues via #N syntax

Linting Rules

1. Language as Programming Language

Treat English/Markdown as a programming language:

  • Use consistent terminology (avoid synonyms)
  • Example: Choose ONE term and stick to it
    • ❌ pull/get/fetch/retrieve
    • ✅ pull (consistently)
  • Define terms once, reference thereafter
  • Use precise, technical language

2. Remove Duplication

  • Eliminate repeated content
  • Use references instead of copying
  • Consolidate similar requirements
  • Extract common patterns to shared sections

3. Minimize Synonyms

Standardize vocabulary across the specification:

Common Synonym Groups (pick ONE per project):

  • obtain/get/retrieve/fetch → get
  • remove/delete/erase → delete
  • create/make/generate/build → create
  • update/modify/change/edit → update
  • validate/verify/check → validate

Read the full file on GitHub · 350 lines

Changes

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.

  1. yesterday First seen · 350 lines · 0 tokens per session scan A c7dc0b7e6b88

Subscribe to this mod's changes

lint 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 2,081 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.