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 agentmods add skills/raphaelmansuy/edgequake/doc-traceability-validatornpx skills add raphaelmansuy/edgequake --skill doc-traceability-validatorgit clone --depth 1 https://github.com/raphaelmansuy/edgequakeWhat 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 | $0.00042 | $0.03073 |
| Opus 5 | $0.00021 | $0.01537 |
| Sonnet 5 | $0.00008 | $0.00615 |
| Haiku 4.5 | $0.00004 | $0.00307 |
Grade A, and why
doc-traceability-validator 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 3d 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 — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Traceability Validator Skill
Validate and maintain accurate traceability between code annotations (@implements FEATXXXX) and documentation registries (features.md, business_rules.md, use_cases.md). This skill detects gaps, collisions, and broken cross-references that compromise documentation accuracy.
When to use
Use this skill when you need to:
- Audit documentation accuracy: Verify all code features are documented
- Detect ID collisions: Find duplicate FEAT/BR/UC IDs before they break traceability
- Find undocumented features: Discover @implements annotations missing from registries
- Validate cross-references: Ensure FEAT↔BR↔UC links are valid
- Enforce namespace allocation: Verify features use correct ID ranges
- Generate registry entries: Auto-create documentation from code annotations
- CI/CD quality gates: Block PRs with documentation gaps
- Track documentation coverage: Monitor doc completeness over time
Core concepts
Traceability Chain
The validation framework ensures bidirectional traceability:
Code (@implements FEATXXXX) ←→ features.md ←→ business_rules.md ←→ use_cases.md
Chain integrity requires:
- Every @implements annotation has a features.md entry
- Every features.md entry references valid BR/UC IDs
- Every BR references valid FEAT IDs
- Every UC references valid BR/FEAT IDs
Validation Dimensions
| Dimension | Weight | Description |
|---|---|---|
| Completeness | 40% | % of code @implements that have docs |
| Uniqueness | 30% | % of IDs that are unique (no collisions) |
| Cross-refs | 20% | % of BR/UC references that resolve |
| Namespace | 10% | % of IDs in correct allocated ranges |
Composite Score:
Score = (0.40 × Completeness) + (0.30 × Uniqueness)
+ (0.20 × CrossRefs) + (0.10 × Namespace)
Namespace Allocation
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 402 lines · 42 tokens per session scan A 5432edc4f884
doc-traceability-validator is a skill published in the GitHub repository raphaelmansuy/edgequake (2,080 stars, last pushed 3d ago), licensed Apache-2.0. It adds 42 tokens to every session and 3,073 once invoked, about $0.0002 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
jurisd-research
Expert Australian/NZ legal research and AGLC4 citation using the jurisd MCP server. Use when finding cases or legislation (AustLII), looking up a provision offline, formatting or resolving citations, building a pinpoint, tracing who-cites-what, or producing an AGLC4 bibliography. Triggers on case law, legislation…
harness-node-splitter
Split a workflow description into constrained harness nodes using the chapter's rule "nodes differ by tool surface, not by prompt." Given candidate operations each with a declared tool set, merge the ones whose tool surfaces overlap >= 80% (prompt variations of one role) and split the ones with distinct tool surfaces…
draft-tool-trust-verifier
Establish trust in a tool by verification, not by its self-description. Flags marketing-gamed tool descriptions ("industry-leading", "trusted by Fortune 500"), requires structured testable capabilities instead of free-text claims, tracks a performance-based trust score (neutral start, successes up, failures and slow…
dual-graph-router
Route an incoming request to the VERTICAL knowledge graph (what the agent knows — a single relationship/temporal traversal), the HORIZONTAL workflow graph (how the agent acts — a decomposed multi-step process), BOTH (a workflow whose nodes query the knowledge graph and write results back), or UNROUTABLE (neither fits…
eight-pillar-readiness-map
Map an agentic-graph system's current capabilities across the eight pillars of Agentic GraphRAG Ch2 (knowledge representation, memory, reasoning, planning, tool orchestration, structured output, self-evolution, optimization), respect the chapter's layering (each pillar depends on the ones before it), flag dependency…
cost-performance-scorer
Score a multi-model routing policy on cost versus quality using the two metrics that actually decide selective intelligence: cost per successful completion (not cost per token) and a per-node quality parity threshold with domain-specific failure weights. Wraps a NodeInvocation log, computes cost-per-success and p95…