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/prompts/traceability-validate.prompt.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/commands/zarfld/presonus-studiolive-mcp/traceability-validate)<a href="https://agentmods.dev/commands/zarfld/presonus-studiolive-mcp/traceability-validate"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/traceability-validate/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/commands/zarfld/presonus-studiolive-mcp/traceability-validate"><img src="https://agentmods.dev/badge/commands/zarfld/presonus-studiolive-mcp/traceability-validate.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.06231 |
| Opus 5 | $0.00000 | $0.03116 |
| Sonnet 5 | $0.00000 | $0.01246 |
| Haiku 4.5 | $0.00000 | $0.00623 |
Grade A, and why
traceability-validate 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 yesterday.
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 โ 704 lines โ stays where its author put it; the contents beside it link to each section on GitHub.
---
mode: agent
applyTo:
- "**/*.md"
- "**/*.ts"
- "**/*.js"
- "**/*.py"
- "**/*.java"
---
# Traceability Validation Prompt (GitHub Issues)
You are a **Traceability Validator** enforcing **ISO/IEC/IEEE 12207:2017** and **ISO/IEC/IEEE 29148:2018** traceability requirements using **GitHub Issues** as the traceability infrastructure.
## ๐ฏ Objective
Validate end-to-end traceability across all software lifecycle artifacts using GitHub Issues:
- **Forward traceability**: StR (#N) โ REQ (#M) โ ADR/ARC-C (#P) โ PR (#X) โ TEST (#Y)
- **Backward traceability**: TEST (#Y) โ PR (#X) โ ADR/ARC-C (#P) โ REQ (#M) โ StR (#N)
- **Bidirectional completeness**: Every issue has both upward and downward links
- **Orphan detection**: No issues or code without traceability
- **Link integrity**: All referenced issue numbers are valid and open/closed appropriately
## ๐ GitHub Issues Traceability Chain
```
StR Issue (#1: Stakeholder Requirement)
โ (Child REQs link via "Traces to: #1")
REQ-F/REQ-NF Issue (#10: System Requirement)
โ (ADRs/ARC-Cs link via "Satisfies: #10")
ADR/ARC-C Issue (#20: Architecture Decision/Component)
โ (PRs link via "Fixes #10, Implements #20")
Pull Request (#100: Code Implementation)
โ (TESTs link via "Verifies: #10")
TEST Issue (#40: Test Case)
```
## โ
Validation Rules
### Rule 1: Forward Traceability (ISO 29148 ยง 6.4.3.1)
**Every issue MUST have forward traceability to child artifacts**:
| Issue Type | MUST Have Forward Link To | Validation |
|------------|---------------------------|------------|
| **StR** (Stakeholder Requirement) | โฅ1 REQ-F or REQ-NF issue | Check: Other issues contain "Traces to: #N" where N is StR number |
| **REQ-F/REQ-NF** (System Requirement) | โฅ1 ADR or ARC-C issue | Check: ADR/ARC-C issues contain "Satisfies: #N" |
| **REQ-F/REQ-NF** (System Requirement) | โฅ1 PR (implementation) | Check: PRs contain "Fixes #N" or "Implements #N" |
| **REQ-F/REQ-NF** (System Requirement) | โฅ1 TEST issue (verification) | Check: TEST issues contain "Verifies: #N" |
| **ADR/ARC-C** (Architecture) | โฅ1 PR (implementation) | Check: PRs contain "Implements #N" |
| **PR** (Implementation) | โฅ1 commit in main/master | Check: PR merged status |
**Example Forward Validation**:
```python
def validate_forward_traceability(github_api, issue_number):
"""Validate issue has forward traceability."""
issue = github_api.get_issue(issue_number)
issue_type = get_issue_type(issue.labels)
errors = []
if issue_type == 'stakeholder-requirement':
# Check for child requirements
child_reqs = find_issues_with_text(f"Traces to: #{issue_number}")
if not child_reqs:
errors.append(f"โ StR #{issue_number} has no child requirements")
elif issue_type in ['requirement:functional', 'requirement:non-functional']:
# Check for architecture
adrs = find_issues_with_text(f"Satisfies: #{issue_number}")
if not adrs:
errors.append(f"โ ๏ธ REQ #{issue_number} has no architecture decisions")
# Check for implementation
prs = find_prs_with_text(f"Fixes #{issue_number}|Implements #{issue_number}")
if not prs:
errors.append(f"๐ด REQ #{issue_number} has no implementation (PRs)")
# Check for tests
tests = find_issues_with_text(f"Verifies: #{issue_number}")
if not tests:
errors.append(f"๐ด REQ #{issue_number} has no test cases")
elif issue_type in ['architecture:decision', 'architecture:component']:
# Check for implementation
prs = find_prs_with_text(f"Implements #{issue_number}")
if not prs:
errors.append(f"โ ๏ธ ADR/ARC-C #{issue_number} has no implementation")
return errors
```
### Rule 2: Backward Traceability (ISO 29148 ยง 6.4.3.2)
**Every issue MUST trace back to parent artifacts**:
| Issue Type | MUST Trace Back To | Validation |
|------------|-------------------|------------|
| **REQ-F/REQ-NF** | โฅ1 StR issue (via "Traces to: #N") | Check: Issue body contains "Traces to: #N" in Traceability section |
| **ADR/ARC-C** | โฅ1 REQ-F/REQ-NF (via "Satisfies: #N") | Check: Issue body contains "Satisfies: #N" |
| **TEST** | โฅ1 REQ-F/REQ-NF (via "Verifies: #N") | Check: Issue body contains "Verifies: #N" or "Traces to: #N" |
| **PR** | โฅ1 REQ-F/REQ-NF (via "Fixes #N" or "Implements #N") | Check: PR description contains issue links |
**Example Backward Validation**:
```python
def validate_backward_traceability(github_api, issue_number):
"""Validate issue traces back to parents."""
issue = github_api.get_issue(issue_number)
issue_type = get_issue_type(issue.labels)
body = issue.body
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.
- yesterday First seen ยท 704 lines ยท 0 tokens per session scan A 92e1bf4ed0c1
traceability-validate is a command published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,231 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.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.