Borrowing it
Nothing to install: this file belongs to dinhnguyenngoc/spec-driven-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dinhnguyenngoc/spec-driven-claude-code/main/.claude/commands/test.mdgit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWrote 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/commands/dinhnguyenngoc/spec-driven-claude-code/test)<a href="https://agentmods.dev/commands/dinhnguyenngoc/spec-driven-claude-code/test"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/test/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/commands/dinhnguyenngoc/spec-driven-claude-code/test"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/test.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.00013 | $0.05619 |
| Opus 5.5 | $0.00005 | $0.02248 |
| Sonnet 5.5 | $0.00003 | $0.01124 |
| Haiku 4.5 | $0.00001 | $0.00562 |
Grade A, and why
test 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 1mo 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test — Quality Gate Testing
"Tests are proof, not afterthought."
Purpose
Verify code works correctly in production-like environment with real dependencies (database, cache). This is the quality gate before /review.
Workspace Mode: if the session root declares
Mode: workspace→ resolve the target repo perCLAUDE.md§Workspace Mode before anything else; every path, probe, and gate below is relative to the target repo, and the workspace disk-check applies at the gate.
Stack Profile note: read
Project Profilefirst. Core = Node.js →rules/overrides/test-nodejs.mdreplaces the test stack (Jest/Vitest instead of xUnit/Moq/FluentAssertions;@testcontainers/*fixtures +prisma migrate deployper its §Template B; coverage vianpm test -- --coverage) — thedotnetcommands in this file map accordingly. Database → the TestContainers image follows the Profile: SQL Server (default) · Oracle → Oracle XE/Free · MySQL →mysql:8.0· PostgreSQL →postgres:16-alpine· MongoDB →mongo:7.0(seerules/overrides/database-*.md). Observability ELK →rules/overrides/monitoring-elk.md. On Apple Silicon (arm64): swap the SQL Server image toazure-sql-edge+ a TCP/port-wait — the defaultmssql/server:2022image segfaults under qemu; seerules/testing.mdTemplate B arm64 note.
Prerequisites
- Code implemented via
/build - Docker Desktop installed and running (REQUIRED)
Test Engineer Responsibilities
/test differs from /build:
| Aspect | /build (Developer) | /test (Test Engineer) |
|---|---|---|
| Focus | Write tests while implementing | Verify, supplement, and re-run with real engines |
| Tests ADDED | Unit (Mock) + Integration (In-Memory) | TestContainers + E2E |
| Tests EXECUTED | Unit (Mock) + Integration (In-Memory) | Everything — re-runs /build's suite (Unit + In-Memory + frontend Vitest) AND adds TestContainers + Playwright E2E |
| Docker | ❌ Not required | ✅ Required |
| Goal | Feature works | Feature works in production-like env, with no regressions |
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.
- 1mo ago First seen · 324 lines · 13 tokens per session scan A ff9e6c2f32e8
test is a command published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (21 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 5,619 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-08-30.
Other commands, from other repositories
spec-impl
Execute spec tasks using TDD methodology.
generate-widget
Génération Widget Flutter avec Tests.
a11y-audit
Audit Accessibilité WCAG 2.2 AAA.
check-testing
Angular Test Coverage and Quality Analysis.
recette
Tests d'acceptance automatises avec Claude in Chrome.
regression
Voir et gerer le registre de tests de regression QA Recette.