Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/andreaswasita/copilot-agents-dojonpx agentmods add skills/andreaswasita/copilot-agents-dojo/traceability-gateWrote 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/andreaswasita/copilot-agents-dojo/traceability-gate)<a href="https://agentmods.dev/skills/andreaswasita/copilot-agents-dojo/traceability-gate"><img src="https://agentmods.dev/badge/skills/andreaswasita/copilot-agents-dojo/traceability-gate.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00014 | $0.01248 |
| Opus 5 | $0.00007 | $0.00624 |
| Sonnet 5 | $0.00003 | $0.00250 |
| Haiku 4.5 | $0.00001 | $0.00125 |
Grade A, and why
traceability-gate 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 8d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traceability Gate
The single governance gate for the TOGAF red thread: no artifact at layer N+1 may persist unless it carries a verified link to a parent at layer N. The skill does NOT elicit requirements and does NOT derive new ones; its only job is to refuse to let unlinked artifacts live.
When to Use
- Before any pull request that touches
requirements/**or any skill that emits artifacts under it. - Before promoting a curator-proposed skill from
optional-skills/toskills/— learned skills must pass the same gate as live delivery. - During Phase B → C and Phase C → D transitions, to prove the cascade is intact before architecture commits to a design.
- After every batch run of
derive-nfr-from-driverorderive-security-from-risk. - NOT as a substitute for elicitation — the gate verifies linkage, not quality of requirements. A bad requirement linked to a bad parent still passes the gate.
Prerequisites
- The engagement directory exists at
requirements/<engagement>/. spec/artifact-schema.mddefines the frontmatter contract.scripts/verify-traceability.shis executable.
The gate is allowed to be called against an empty engagement directory — it reports zero artifacts and exits 0. That is the seed state, not a failure.
How to Run
# Full traceability check for one engagement
bash scripts/verify-traceability.sh requirements/<engagement>
# CI / strict mode — warnings (e.g. unratified) become failures
bash scripts/verify-traceability.sh --strict requirements/<engagement>
# Generate the RTM as a byproduct of the gate
bash scripts/gen-rtm.sh requirements/<engagement>
# Roll the gate into the dojo-wide gate
bash scripts/verify.sh # invokes run_traceability_checks
Quick Reference
| Action | Tool | Notes |
|---|---|---|
| Run gate locally | bash scripts/verify-traceability.sh requirements/<engagement> |
Exit 0 = lineage intact. |
| Run gate strict | bash scripts/verify-traceability.sh --strict … |
CI default. |
| Regenerate RTM | bash scripts/gen-rtm.sh requirements/<engagement> |
Writes docs/rtm-<engagement>.md. |
| Full dojo gate | bash scripts/verify.sh |
Includes the traceability check. |
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.
- 8d ago First seen · 131 lines · 14 tokens per session scan A 5d1f9ca8b826
traceability-gate is a skill published in the GitHub repository andreaswasita/copilot-agents-dojo (51 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 1,248 once invoked, about $0.0001 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-30.
Other skills, from other repositories
compliance
Use when scoping which regulatory frameworks bind a business — SOC 2, ISO 27001, HIPAA, PCI DSS, EU AI Act, DORA, NIS2 — building a control register with owners and evidence, or standing up the cadence that keeps it audit-ready. NOT drafting privacy-policy/ROPA/DPA or ToS text (that is gdpr-privacy, terms-conditions)…
conducting-cyber-risk-assessment-with-nist-800-30
Conduct a defensible cybersecurity risk assessment using the NIST SP 800-30 Rev 1 methodology: prepare scope and a risk model, identify threat sources and threat events, identify vulnerabilities and predisposing conditions, determine likelihood and impact, compute risk, and communicate results as a prioritized risk…
implementing-gdpr-data-protection-controls
The General Data Protection Regulation (EU) 2016/679 (GDPR) is the EU's comprehensive data protection law governing the collection, processing, storage, and transfer of personal data. This skill cover.
decision-ledger
A session record for tracking unresolved decisions and drafting them into `.governance/claims/` when they are settled. It preserves both the decision and the reason behind it.
governance-bootstrap
A guided checklist for creating a project's governance system from scratch when no governance exists.
session-grounding
A session-start procedure for checking the current facts, scope, and work track in a governed project before taking action.