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/Skills/repo-truth-maintenance/SKILL.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/skills/zarfld/presonus-studiolive-mcp/repo-truth-maintenance)<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/repo-truth-maintenance"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/repo-truth-maintenance/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/skills/zarfld/presonus-studiolive-mcp/repo-truth-maintenance"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/repo-truth-maintenance.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.00032 | $0.01243 |
| Opus 5 | $0.00016 | $0.00622 |
| Sonnet 5 | $0.00006 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
repo-truth-maintenance 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo truth maintenance
Use this skill when
Use this skill when editing or reviewing:
README.md- status/version/release claims
- hardware support statements
- license text
- “complete”, “field-ready”, “v1.0”, “all”, “fully”, “production-ready”, “validated”, or similar claims
- generated or template-derived process text
- documentation that lists MCP tools/resources, supported mixer models, firmware versions, or validation coverage
Goal
Prevent the repository from claiming more than the code and verification artifacts prove.
The repository may describe planned or inferred capability, but it must label it explicitly. The README must be a product-status document, not a mixture of product truth and generic lifecycle-template marketing.
Required claim categories
Every nontrivial capability claim must fit one category:
| Category | Meaning | Allowed wording |
|---|---|---|
verified |
Confirmed by automated tests or hardware evidence linked from the repo | “verified on …”, “tested by …” |
implemented-unverified |
Code exists, but no HIL/probe evidence yet | “implemented, not hardware-verified” |
inferred |
Derived from live state keys or reverse engineering, not probe-confirmed | “inferred from live state” |
probe-required |
Requires operator-driven diff/probe before reliable use | “probe required” |
stub |
Tool/schema exists but deliberately returns limited result | “stub”, “returns instructions only” |
planned |
Backlog item only | “planned”, “not implemented” |
unsupported |
Out of scope or blocked | “not supported” |
Procedure
- Inspect implementation before editing documentation.
- Check
packages/presonus-mcp-server/src/tools.tsfor registered tools. - Check
packages/presonus-mcp-server/src/resources.tsfor registered resources. - Check
package.jsonand package-levelpackage.jsonfiles for actual version numbers and scripts. - Check HIL fixtures, HIL tests, captured probe output, and validation docs before writing hardware-support claims.
- Check
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 · 117 lines · 32 tokens per session scan A 556b6d63b45f
repo-truth-maintenance is a skill published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,243 once invoked, about $0.0002 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 skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.