What is repository-audit?

A repository audit command that reviews an existing code repository against software development and requirements-management practices. It identifies gaps, proposes a migration plan, estimates effort, and suggests gradual adoption.

Use it to inspect repository structure, find documentation and traceability gaps, prioritise corrective work, and plan adoption of an issue-driven workflow.

It shows what is missing from the current project structure and process instead of requiring a team to compare everything manually with a target setup.

How zarfld/presonus-studiolive-mcp configures GitHub Copilot

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/repository-audit.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/repository-audit/github.svg)](https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/repository-audit)

Your own site

<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/repository-audit"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/repository-audit/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/repository-audit"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/repository-audit.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 15,834 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.15834
Opus 5.5	$0.00000	$0.06334
Sonnet 5.5	$0.00000	$0.03167
Haiku 4.5	$0.00000	$0.01583

Measured 1mo ago against content hash 06ff392e6c91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

repository-audit 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.

.github/prompts/repository-audit.prompt.md · 1,900 lines

How it starts

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

Repository Audit Prompt

You are a Software Quality Auditor following ISO/IEC/IEEE 12207:2017 and ISO/IEC/IEEE 29148:2018 standards.

🎯 Objective

Perform comprehensive audit of existing repository to:

Assess current compliance with spec-driven development standards
Identify gaps between current state and template requirements
Generate migration roadmap with prioritized action items
Estimate effort required for full compliance
Provide recommendations for gradual adoption

🔍 Repository Analysis Framework

Step 1: Structure Analysis

Analyze repository structure against template:

Expected Structure (GitHub Issues-First Template):

project/
├── README.md                           # Project overview (references GitHub Issues)
├── docs/                               # Supplementary documentation (MUST reference issues)
│   ├── 01-stakeholder-requirements/    # Phase 01 (optional supplementary docs)
│   │   ├── stakeholder-interviews.md   # References StR issues via #N
│   │   └── business-case.md            # References StR issues via #N
│   ├── 02-requirements/                # Phase 02 (optional supplementary docs)
│   │   └── user-stories.md             # References REQ-F issues via #N
│   ├── 03-architecture/                # Phase 03 (C4 diagrams reference ADR/ARC-C)
│   │   ├── diagrams/                   # C4 Context, Container, Component
│   │   └── architecture-views.md       # References #ADR and #ARC-C issues
│   ├── 04-design/                      # Phase 04 (design docs reference #ARC-C)
│   │   ├── components/                 # Component designs referencing ARC-C issues
│   │   └── interfaces/                 # API specs referencing ARC-C issues
│   ├── 05-implementation/              # Phase 05 (code with issue references)
│   ├── 06-integration/                 # Phase 06 (integration docs)
│   ├── 07-verification-validation/     # Phase 07 (test results)
│   ├── 08-transition/                  # Phase 08 (deployment docs)
│   └── lifecycle-guide.md              # Process documentation
├── .github/
│   ├── ISSUE_TEMPLATE/                 # Issue templates (StR, REQ-F, REQ-NF, ADR, ARC-C, TEST)
│   ├── prompts/                        # Copilot prompts
│   └── workflows/                      # CI/CD with traceability validation
├── src/                                # Source code (docstrings reference issues)
├── tests/                              # Test code (tests reference issues)
└── package.json                       # Dependencies & scripts

Read the full file on GitHub · 1,900 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.

1mo ago First seen · 1,900 lines · 0 tokens per session scan A 06ff392e6c91

Subscribe to this mod's changes

repository-audit is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 15,834 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.

Planning Project management audio mcp mixer model-context-protocol model-context-protocol-server presonus

presonus-studiolive-mcp: Command for GitHub Copilot

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Repository Audit Prompt

🎯 Objective

🔍 Repository Analysis Framework

Step 1: Structure Analysis

Expected Structure (GitHub Issues-First Template):

What this file has done since we first saw it

Other commands, from other repositories

broadcast

gsd:ship

backlog

service-assessment

roadmap

issue-tracker