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 naodeng/awesome-qa-skills --skill requirement-traceability-analysisgit clone --depth 1 https://github.com/naodeng/awesome-qa-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/naodeng/awesome-qa-skills/requirement-traceability-analysis)<a href="https://agentmods.dev/skills/naodeng/awesome-qa-skills/requirement-traceability-analysis"><img src="https://agentmods.dev/badge/skills/naodeng/awesome-qa-skills/requirement-traceability-analysis/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/skills/naodeng/awesome-qa-skills/requirement-traceability-analysis"><img src="https://agentmods.dev/badge/skills/naodeng/awesome-qa-skills/requirement-traceability-analysis.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.00053 | $0.01567 |
| Opus 5.5 | $0.00021 | $0.00627 |
| Sonnet 5.5 | $0.00011 | $0.00313 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
requirement-traceability-analysis 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
16 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.
- agents/openai.yaml 465 B
- evals/cases/basic-success.yaml 1.4 KB
- evals/cases/coverage-incomplete-input.yaml 941 B
- evals/cases/coverage-scope-boundary.yaml 1.2 KB
- evals/cases/coverage-success.yaml 1.1 KB
- evals/cases/domain-method-regression.yaml 1.6 KB
- evals/cases/edge-incomplete-input.yaml 1012 B
- evals/cases/edge-scope-boundary.yaml 1.3 KB
- evals/eval.yaml 625 B
- evals/fixtures/check_domain_decisions.py 3.8 KB runs code
- evals/fixtures/check-domain-decisions.sh 95 B runs code
- evals/fixtures/domain-oracle.json 269 B
- evals/local-rules.json 144 B
- evals/trigger-prompts.csv 902 B
- prompts/requirement-traceability-analysis.md 7.3 KB
- references/domain-decision-example.md 2.1 KB
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 Changed · +10 lines 6291e14fbdcd
- 1mo ago First seen · 76 lines · 53 tokens per session scan A 360a84756afe
requirement-traceability-analysis is a skill published in the GitHub repository naodeng/awesome-qa-skills (260 stars, last pushed 3d ago), with no licence file. It adds 53 tokens to every session and 1,567 once invoked, about $0.0002 per session on Opus 5.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-09-15.
Other skills, from other repositories
Browser Agent QA Testing
Teach agents to use AI browser agents for exploratory and smoke QA with step budgets, evidence-based assertions, guardrails, and Playwright conversion.
cypress-cloud-cli
Runs the cy-cloud CLI to inspect Cypress Cloud organizations, projects, runs, specs, tests, failure screenshots, and Test Replay data. Use when the user mentions Cypress Cloud, cy-cloud, cypress-cloud-cli, a Cloud run or test URL, failing or flaky Cypress tests, Test Replay, run triage, Cloud artifacts, or asks why a…
pair-programming
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Features automatic role switching, continuous code review, security scanning, and performance optimization with…
visual-proof
Capture before/after screenshot evidence of a web page at real breakpoints (375, 768, 1440) in both light and dark themes, using Playwright against a local dev server or a deployed URL. Use before starting any visual change to capture the current state, and again after to prove the delta. Also use when asked to "show…
neutron-log
Measure whether a token-saving tool actually saves tokens and keeps answers correct. Use before adopting or recommending RTK, headroom, caveman or any compressor, after changing a hook or instruction file, and when someone quotes a savings percentage. Runs a same-task before and after protocol and records only…
verification-loop
After a feature or refactor on this Windows estate, run six checks in order and write a PASS or FAIL note before a draft pull request. Use when work is about to be committed, pushed, or handed to another harness.