test

A command for running the tests defined by a project's technology instructions and recording a concise result in the pipeline log. It can select changed tests, the full suite, a file, or coverage reporting.

In plain words
What is it for?
Use it to run tests after changes, target a specific test file, run the complete suite, or inspect coverage and failures with line references.
Why use it?
It avoids guessing which test runner or test scope to use and produces consistent pass, failure, skipped-test, duration, and coverage information without changing source code.

Command

Part of the project-scaffolder plugin — 7 skills, 19 commands, 2 hooks shipped together

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.

agentmods
npx agentmods add commands/valsecchi75/project-scaffolder/test
Clone the repo
git clone --depth 1 https://github.com/valsecchi75/project-scaffolder

Or install project-scaffolder, the plugin that ships this one along with the rest of its 7 skills, 19 commands, 2 hooks.

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 335 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.00335
Opus 5 $0.00009 $0.00168
Sonnet 5 $0.00003 $0.00067
Haiku 4.5 $0.00002 $0.00034

Measured 2d ago against content hash a478af5b76e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

commands/test.md · 47 lines

What it actually says

/test

Run tests declared in wiki/tech-stack.md.

Usage

/test                  — smart default (changed files)
/test --changed        — only tests related to changed files
/test --all            — full suite
/test --coverage       — include coverage report
/test --file <path>    — specific test file

Steps

  1. Read wiki/tech-stack.md to identify the test runner (flutter test, jest, pytest, etc.).
  2. Resolve scope from flags.
  3. Execute the test command.
  4. Parse the result: pass/fail counts, failing tests with line references.
  5. If --coverage: parse coverage percentage per file and compute delta vs. last run if recorded.
  6. Append a summary to logs/pipeline/YYYY-MM-DD.md.

Output format

## Test — <scope>
- **Runner:** [tool]
- **Result:** ✅ N passed / ❌ M failed / ⏭ K skipped
- **Duration:** Ns
- **Failures:**
  - test/path.dart:23 — expected X got Y
- **Coverage:** NN% (delta vs last run: +/-X%)

Rules

  • Never modify source code inside this command — that is /task's job.
  • If no tests exist yet: report clearly and suggest creating one.
  • Fail fast on infrastructure errors (missing dependencies, compile errors).
  • Honest reporting: don't smooth over flaky tests; flag them explicitly.
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. 2d ago First seen · 47 lines · 17 tokens per session scan A a478af5b76e4

Subscribe to this mod's changes

test is a command published in the GitHub repository valsecchi75/project-scaffolder (9 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 335 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-08-31.