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/alonf/specrew/specrew-traceability-checknpx skills add alonf/specrew --skill specrew-traceability-checkgit clone --depth 1 https://github.com/alonf/specrewWrote 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/alonf/specrew/specrew-traceability-check)<a href="https://agentmods.dev/skills/alonf/specrew/specrew-traceability-check"><img src="https://agentmods.dev/badge/skills/alonf/specrew/specrew-traceability-check.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 | $0.00038 | $0.00538 |
| Opus 5 | $0.00019 | $0.00269 |
| Sonnet 5 | $0.00008 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
specrew-traceability-check 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 4d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specrew-traceability-check
Type: Analysis Skill
Schema: v1
Status: Active planning/review method
Purpose
Validate that the plan is safe to execute by proving every task traces to authority and every in-scope requirement has coverage.
When to Use
- During Planning before approval
- During Review when scope or requirement coverage is questioned
- On demand when a task looks orphaned or a requirement looks uncovered
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
| iteration_plan_path | path | Yes | Path to iterations/NNN/plan.md |
| spec_path | path | Yes | Path to the authoritative spec file |
| requirement_scope | array? | No | Optional filter for specific requirements |
Process
- Parse the plan task table and collect task IDs, requirement refs, story refs, owners, and statuses
- Parse the spec and identify the in-scope requirements
- Build both:
- requirement -> tasks
- task -> requirement
- Fail the check on:
- orphan tasks
- stale or invalid requirement references
- uncovered in-scope requirements
- tasks missing owner, effort, or story metadata
- Return concrete fixes, not just a percentage
Outputs
| Output | Type | Description |
|---|---|---|
| verdict | enum: PASS, FAIL | Traceability check result |
| coverage_ratio | float | Percentage of requirements with tasks |
| orphan_tasks[] | array | Tasks with missing or invalid requirement refs |
| uncovered_requirements[] | array | Requirements with no tasks |
| partial_requirements[] | array | Requirements partially implemented |
| fix_actions[] | array | Plan edits required before execution can begin |
Side Effects
None. This is a pre-execution gate.
Error Handling
- If
iteration_plan_pathis missing: return FAIL withplan file missing - If
spec_pathis missing: return FAIL withspec file missing - If plan or spec parsing fails: return FAIL with the parsing problem
Review Standard
What ships with it
1 file 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.
- 4d ago First seen · 71 lines · 38 tokens per session scan A 52ce2270a029
specrew-traceability-check is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 538 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…