agentmods.dev

traceability-audit

traceability-audit is a command for GitHub Copilot from HoangNguyen0403/agent-skills-standard. It costs 19 tokens per session (530 once invoked), scanned A, original, MIT.

A report that connects requirements, acceptance criteria, implementation, tests, and release notes. Acceptance criteria are the specific conditions a feature must meet before it is accepted.

In plain words
What is it for?
Use it to map each requirement to code and verification, classify coverage as covered, partial, missing, or deferred, and identify gaps.
Why use it?
It exposes requirements with no implementation, tests, or release evidence before a handoff or release.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

not rated 565repo +4 3d ago A scan 19 tokens original MIT

Good fit Use it to map each requirement to code and verification, classify coverage as covered, partial, missing, or deferred, and identify gaps.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/hoangnguyen0403/agent-skills-standard/traceability-audit
View source ↗ HoangNguyen0403/agent-skills-standard npmjs.com
Install

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.

Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for traceability-audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/traceability-audit/github.svg)](https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/traceability-audit)
Your own site
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/traceability-audit"><img src="https://agentmods.dev/badge/commands/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.

agentmods 80×15 button for traceability-audit

Your own site · 80×15
<a href="https://agentmods.dev/commands/hoangnguyen0403/agent-skills-standard/traceability-audit"><img src="https://agentmods.dev/badge/commands/hoangnguyen0403/agent-skills-standard/traceability-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 530 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00530
Opus 5 $0.00010 $0.00265
Sonnet 5 $0.00004 $0.00106
Haiku 4.5 $0.00002 $0.00053

Measured 6d ago against content hash 21104f6f32bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 6d 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.

.github/prompts/traceability-audit.prompt.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Traceability Audit Workflow

Goal: Prove every acceptance criterion has implementation and verification evidence before release or handoff.

Steps

  1. 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.
  2. Build trace map:
    • BRD objective -> PRD requirement ID.
    • PRD requirement ID -> SRS/FRS contract.
    • AC -> implementation file/function.
    • AC -> automated test, manual/Zephyr TC, or verification step.
    • Release note -> shipped user-visible change.
  3. Classify each AC:
    • Covered: code and verification evidence exists.
    • Partial: code or evidence incomplete.
    • Missing: no implementation or no verification.
    • Out of scope: explicitly deferred with owner/link.
  4. Flag gaps:
    • Missing requirement mapping.
    • Missing AC implementation.
    • Missing test or manual coverage.
    • Release note missing shipped user impact.

Runtime Contract

  • Use pre-release or handoff to prove requirement-to-evidence coverage.
  • Required inputs: PRD/SRS with AC list plus implementation, test, and release artifacts to map against.
  • Return BLOCKED only when no requirement or AC list exists to trace.

Handoff Payload

  • slug, requirement map, gap classification, outcome report, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# Traceability Audit

## Summary

## Requirement Map

| Requirement | SRS/FRS Contract | Verification | Status |
| --- | --- | --- | --- |
| [REQ] | [contract] | [test/evidence] | [status] |

## Gaps

## Outcome Report
feature_status: implemented | partially_implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: implement-feature | dev-fix | deploy-release

## Next Workflow

## Cost Report
Call `get_session_cost(workflow="traceability-audit")` before final handoff.

Read the full file on GitHub · 65 lines

Changes

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.

  1. 6d ago First seen · 65 lines · 19 tokens per session scan A 21104f6f32bb

Subscribe to this mod's changes

traceability-audit is a command published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 19 tokens to every session and 530 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-09-06.

Project managementReactbest-practicescoding-standardsflutternestjsnextjs
Related

Other commands, from other repositories

plan

PM planning workflow that gathers requirements, decomposes them into prioritized tasks, defines API contracts, and produces both a machine-readable plan and a human-readable tracker in docs/plans/.

first-fluke/fullstack-starter · 35 tokens

schedule

Register a scheduled agent job from a natural-language schedule request — parse the interval, resolve agent-id + prompt + workspace, call oma schedule:add, then confirm with oma schedule:list.

first-fluke/fullstack-starter · 35 tokens

coordinate-pro

Thorough version of coordinate - high-quality development workflow with 11 review steps out of 17.

first-fluke/fullstack-starter · 19 tokens

coordinate

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 20 tokens

exec-plan

Create, manage, and track execution plans as first-class repository artifacts in docs/exec-plans/.

first-fluke/fullstack-starter · 20 tokens

work

Coordinate multiple agents for a complex multi-domain project using PM planning, parallel agent spawning, and QA review.

first-fluke/fullstack-starter · 20 tokens