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 HoangNguyen0403/agent-skills-standard --skill traceability-auditgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/traceability-audit)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/traceability-audit"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/traceability-audit/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/hoangnguyen0403/agent-skills-standard/traceability-audit"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/traceability-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 40 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00024 | $0.00939 |
| Opus 5.5 | $0.00010 | $0.00376 |
| Sonnet 5.5 | $0.00005 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
traceability-audit 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 today.
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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Traceability Audit Skill
[!IMPORTANT] Map requirements, acceptance criteria, implementation, tests, and release artifacts into one traceability report.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
Traceability Audit Workflow
Goal: Prove every acceptance criterion has implementation and verification evidence before release or handoff.
Steps
- Load sources:
- BRD-lite, PRD, SRS/FRS, AC list, implementation plan, changed files, tests, walkthrough, PR comments, release notes.
- Jira/GitHub/GitLab/ADO/Zephyr/Confluence MCPs when configured; otherwise use exported files and local evidence.
- Build trace map across 4 V-Model levels (
skills/quality-engineering/quality-engineering-test-plan-authoring/references/lifecycle-and-roles.md):- BRD objective -> PRD requirement ID <-> Acceptance Testing (UAT/signoff).
- PRD requirement ID -> SRS/FRS contract <-> System Testing (E2E web/mobile scenarios).
- AC -> exact implementation file/function.
- AC -> automated test ID, manual/Zephyr TC, or verification step <-> Integration / Unit Testing.
- Mobile trace (Contract C6): map mobile ACs to app artifact digest/build, OS/device cells, and driver evidence.
- Release note -> shipped user-visible change. Low-risk work uses equivalent existing evidence; four new docs not required.
- Classify each AC & test disposition (STLC Stage 6 Closure):
- Covered / PASS: implementation file/function exists AND fresh verification evidence verified.
- Partial: code or verification evidence incomplete.
- Missing: no implementation or unverified.
- BLOCKED: missing environment, driver, or credential; listed under
missing_evidence. - Deferred / Risk-Accepted: formally waived with named human owner, rationale, and expiry.
- Flag gaps and open defects:
- Missing requirement or V-model interface mapping.
- Missing AC implementation (unmapped file/function).
- Missing test or manual coverage (unmapped automated test, manual/Zephyr TC, or untested device cell).
- Open defect ledger with severity, affected AC impact, and owner.
- Release notes claiming unverified or unreleased capabilities.
- Write run record to
artifacts/runs/[slug]/[compactISO]-traceability-audit.jsonwhen file writes allowed.
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.
- today Changed · +2 lines b33fba4b5c74
- 28d ago Changed · +1 lines 4df3113d45ca
- 1mo ago Changed 732a7713bc47
- 1mo ago First seen · 83 lines · 24 tokens per session scan A 9eff166cac61
traceability-audit is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 939 once invoked, about $0.0001 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-03.
Other skills, from other repositories
browser-automation
Playwright browser automation via MCP. Covers E2E testing, UI review, web scraping, screenshot capture, and general browser interaction. MCP-first — CLI is fallback only.
vue-idioms
Vue 3 Composition API patterns: syntax, reactive state with Pinia stores, reusable composables, and Vitest component testing. Use when developing or refactoring Vue 3 frontend applications.
python-idioms
Modern Python (3.11+) idioms: type annotations, typing Protocols, Pydantic models, asyncio, pytest fixtures, and Ruff/Mypy strict compliance. Use when writing, refactoring, or reviewing Python applications, APIs, or scripts.
testability-patterns
Implementation examples for the three testability rules (I/O isolation, pure logic, dependency direction) across Go, TypeScript, Python, Rust, and Dart. Loaded by reference from architectural-pattern.md — not triggered by file patterns.
testing-strategy
Detailed testing reference material: test doubles strategy, integration test infrastructure (Testcontainers, Firebase emulator), naming conventions per language, test organization patterns. Load when writing tests or setting up test infrastructure. The core mandates (TDD, AAA, pyramid) are in the testing-strategy rule…
react-testing
React testing guidance using React Testing Library and modern patterns.