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/mcp-capability-contract/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/mcp-capability-contract)<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/mcp-capability-contract"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/mcp-capability-contract/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/mcp-capability-contract"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/mcp-capability-contract.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.01057 |
| Opus 5 | $0.00000 | $0.00528 |
| Sonnet 5 | $0.00000 | $0.00211 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
mcp-capability-contract 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 11d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Capability Contract
Purpose
Use this skill whenever an MCP tool, resource, adapter method, README claim, capability matrix entry, or release checklist item is added, changed, reviewed, or marked complete.
This skill prevents the repository from overstating support. A tool that exists in code is not automatically supported. A tool is supported only when implementation, tests, evidence, and documentation agree.
Applies to
- MCP tool inventory
docs/capability-matrix.generated.mddocs/release-readiness-checklist.mdREADME.md- package metadata and examples
- GitHub issues and milestones
- adapter/domain/server packages
Capability states
Use exactly one of these states for each tool or feature.
| State | Meaning |
|---|---|
observed |
Verified against real hardware or a captured real device fixture. |
implemented_unverified |
Real implementation exists, but no HIL or real-device fixture proves correctness. |
inferred |
Behavior is derived from indirect evidence or a guessed mapping/formula. |
probe_required |
The implementation cannot be completed or trusted without a defined hardware probe. |
stub |
User-visible tool exists, but it intentionally returns placeholder/non-verifiable data. |
planned |
Not implemented and not exposed as functional. |
not_supported |
Deliberately out of scope. |
deprecated |
Former capability that should not be used. |
Do not invent alternative labels.
Hard rules
- Never mark a tool as
observedwithout naming the hardware model, firmware version, evidence artifact, and test/probe used. - Never call a user-visible tool "supported" if the code path returns placeholders, empty objects, guessed values, or
not_verifiable. - Never hide uncertainty. If a value is guessed, the response schema and docs must say so.
- Never let README claims be broader than the capability matrix.
- Never upgrade a state because a test was added unless the test asserts the real behavior being claimed.
- Any write-capable tool must also satisfy the
mcp-write-safety-gateskill before it can be marked anything stronger thanimplemented_unverified.
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.
- 11d ago First seen · 130 lines · 0 tokens per session scan A 312c4b3e4916
mcp-capability-contract is a skill published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,057 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…