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/release-readiness-audit/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/release-readiness-audit)<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/release-readiness-audit"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/release-readiness-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.
<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/release-readiness-audit"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/release-readiness-audit.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.00809 |
| Opus 5.5 | $0.00000 | $0.00324 |
| Sonnet 5.5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
release-readiness-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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Readiness Audit
Purpose
Use this skill before publishing, tagging, announcing, or broadening claims about the MCP server.
This audit separates what is actually supported from what is experimental, inferred, stubbed, or blocked by hardware evidence.
Applies to
- README
- npm package metadata
- release notes
- GitHub milestones
- capability matrix
- release-readiness checklist
- MCP tool inventory
- examples and quick-start docs
Required classification
Group all features into:
| Group | Meaning |
|---|---|
| Supported | Observed with model/firmware evidence and tests. |
| Experimental | Implemented but not fully HIL-verified or only safe for controlled testing. |
| Read-only supported | Safe inspection tools with observed data. |
| Write-gated | Mutating tools disabled by default and not claimed safe for live use. |
| Probe required | Requires HIL before support can be claimed. |
| Stub/unavailable | Exposed only as placeholder or not exposed as functional. |
| Not supported | Explicitly out of scope. |
Required workflow
- Build the current tool inventory.
- Compare inventory against capability matrix.
- Compare README claims against capability matrix.
- Compare release checklist against actual tests and HIL evidence.
- Review open issues labelled completed, blocked, HIL, routing, writes, Fat Channel.
- Check that write tools are disabled by default.
- Check that stubs are not advertised as functional.
- Check that model/firmware scope is explicit.
- Produce release decision.
Required output
# Release Readiness Report
## Decision
release / prerelease / do-not-release
## Supported scope
Exact model/firmware/features supported.
## Experimental scope
Implemented but not proven.
## Stub/unavailable capabilities
Visible incomplete tools or docs.
## Blocking issues
Must fix before release.
## Documentation corrections
Claims that must be narrowed.
## Required HIL probes
Probes needed to upgrade capability.
## Recommended version label
Example: 0.1.x experimental-readonly
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 · 170 lines · 0 tokens per session scan A e58c7a65a5d2
release-readiness-audit is a skill 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 809 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-08-31.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
bob-export
Create a Hacker Bob post-release improvement bundle for the currently installed Bob version.