Nexus-acp: Command for Claude Code

.claude/commands/bmad/bmm/workflows/testarch-trace.md

testarch-trace is a command for Claude Code from cosmos-vibe/Nexus-acp. It costs 28 tokens per session (186 once invoked), scanned A, a copy of correct-course, Apache-2.0.

A workflow that links software requirements to tests in a traceability matrix, showing which requirements have checks.

In plain words
What is it for?
It helps build requirements-to-tests coverage records and classify the result as PASS, CONCERNS, FAIL, or WAIVED.
Why use it?
It makes gaps in test coverage visible and provides a quality-gate decision based on the available analysis.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is cosmos-vibe/Nexus-acp's own configuration. It tells Claude Code how to work on Nexus-acp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Nexus-acp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to cosmos-vibe/Nexus-acp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/cosmos-vibe/Nexus-acp/main/.claude/commands/bmad/bmm/workflows/testarch-trace.md
Clone the repo
git clone --depth 1 https://github.com/cosmos-vibe/Nexus-acp

Made for: Claude Code.

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 testarch-trace

README.md
[![agentmods](https://agentmods.dev/badge/commands/cosmos-vibe/nexus-acp/testarch-trace/github.svg)](https://agentmods.dev/commands/cosmos-vibe/nexus-acp/testarch-trace)
Your own site
<a href="https://agentmods.dev/commands/cosmos-vibe/nexus-acp/testarch-trace"><img src="https://agentmods.dev/badge/commands/cosmos-vibe/nexus-acp/testarch-trace/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 testarch-trace

Your own site · 80×15
<a href="https://agentmods.dev/commands/cosmos-vibe/nexus-acp/testarch-trace"><img src="https://agentmods.dev/badge/commands/cosmos-vibe/nexus-acp/testarch-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 186 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 81% copy Near-identical to another mod 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.00028 $0.00186
Opus 5 $0.00014 $0.00093
Sonnet 5 $0.00006 $0.00037
Haiku 4.5 $0.00003 $0.00019

Measured 9d ago against content hash 0d5c5fb38ed4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

testarch-trace 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 9d 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.

Origin

This is a copy

81% identical to correct-course — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/bmad/bmm/workflows/testarch-trace.md · 14 lines

What it actually says

IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:

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. 9d ago First seen · 14 lines · 28 tokens per session scan A 0d5c5fb38ed4

Subscribe to this mod's changes

testarch-trace is a command published in the GitHub repository cosmos-vibe/Nexus-acp (11 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 186 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to correct-course, differing in 6 lines, and is treated as a copy.