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/traceability-enforcement/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/traceability-enforcement)<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/traceability-enforcement"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/traceability-enforcement/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/traceability-enforcement"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/traceability-enforcement.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.00805 |
| Opus 5 | $0.00000 | $0.00402 |
| Sonnet 5 | $0.00000 | $0.00161 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
traceability-enforcement 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traceability Enforcement
Purpose
Use this skill to enforce the repository workflow:
requirement -> architecture/design -> implementation -> tests -> HIL evidence -> capability claim
Agents must not jump directly into code and then mark work complete.
Applies to
- new features
- changed MCP tools
- routing work
- Fat Channel calibration
- write tools
- docs claiming support
- issue closure
- release readiness
- generated inventories
Required trace objects
Each non-trivial feature must have traceability across:
| Trace object | Required for |
|---|---|
| GitHub issue | all user-visible feature work |
| requirement statement | all feature work |
| design note | routing, writes, Fat Channel, protocol mapping |
| implementation files | all code changes |
| unit tests | all deterministic logic |
| integration/tool tests | all MCP tools |
| HIL probe/evidence | hardware behavior |
| capability matrix entry | all MCP tools/features |
| release checklist entry | release-relevant work |
Required workflow
- Identify the feature or claim being touched.
- Find or create the issue.
- State the requirement in one sentence.
- State the design approach before code changes.
- Identify impacted files.
- Identify required tests.
- Identify whether HIL evidence is required.
- Implement only after steps 1-7 are clear.
- Update capability and release docs.
- Produce a traceability table.
Required output
Every run must produce:
| Feature | Issue | Requirement | Design | Code | Unit tests | Tool tests | HIL | Capability matrix | Status |
|---|
Allowed status values:
complete
implemented_unverified
blocked_by_hil
blocked_by_design
stub_only
not_supported
Minimum requirement format
Use concise requirements:
REQ-ROUTING-001: The MCP server shall report, per input channel, whether the channel source is local analog, AVB/stagebox, or unknown, including confidence and raw adapter evidence.
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 · 156 lines · 0 tokens per session scan A 9a7b891d4dc5
traceability-enforcement 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 805 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.