Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ddddjaak/se-skills --skill traceability-matrixgit clone --depth 1 https://github.com/ddddjaak/se-skillsWrote 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/ddddjaak/se-skills/traceability-matrix)<a href="https://agentmods.dev/skills/ddddjaak/se-skills/traceability-matrix"><img src="https://agentmods.dev/badge/skills/ddddjaak/se-skills/traceability-matrix.svg" alt="Measured on agentmods" 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.00164 | $0.04136 |
| Opus 5 | $0.00082 | $0.02068 |
| Sonnet 5 | $0.00033 | $0.00827 |
| Haiku 4.5 | $0.00016 | $0.00414 |
Grade A, and why
traceability-matrix 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 6d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traceability Matrix
Overview
Every SE artifact references other artifacts. Requirements reference their sources. Architecture elements reference their requirements. Specifications reference their architecture. Test cases reference their requirements. These references form a chain. When the chain is intact, you can answer "if we change X, what breaks?" by following the links. When the chain is broken, you discover the breakage during integration testing — or worse, in the field.
This skill extracts all references from all SE artifacts, builds the complete traceability graph, identifies every broken link and uncovered node, and produces a report that tells you exactly what is missing. It runs across artifacts rather than producing one — it is the quality assurance step of the SE workflow, the "lint" that verifies every requirement has a design, every design element is tested, and every test validates something required.
When to Use
- After completing any SE artifact — to verify that it properly links to upstream and downstream artifacts
- Before a milestone review (requirements freeze, design freeze, test readiness) — to produce the formal traceability evidence
- When scope changes — to assess which design elements and test cases are affected by a requirement change
- After a
design-reviewresolution — to verify that fixes have not broken traceability links - Auditing or certification requires formal traceability documentation
- Integrating artifacts from multiple authors — to verify cross-author consistency
When NOT to use:
- No SE artifacts exist yet (run the upstream skills first)
- The change to an artifact is purely editorial (typo fix, reformatting — reference IDs unchanged)
- There is only one artifact (traceability requires at least two artifacts to trace between)
- The user explicitly asks for a quick coverage check (do it manually, don't invoke the full skill)
The Process
EXTRACT ──→ LINK ──→ COVERAGE ──→ GAP-ANALYSIS ──→ REPORT
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
Parse all Build Calculate Identify Produce
artifact trace coverage orphans, traceability
references chains metrics gaps, & report
over-coverage
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.
- 6d ago First seen · 310 lines · 164 tokens per session scan A 59e58821c4e0
traceability-matrix is a skill published in the GitHub repository ddddjaak/se-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 164 tokens to every session and 4,136 once invoked, about $0.0008 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
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.