test

test is a command for Claude Code from nxtg-ai/forge-plugin. It costs 8 tokens per session (894 once invoked), scanned A, original, MIT.

A test-running command that executes selected parts of a project’s test suite and converts the raw output into a structured report. It summarizes passes, failures, skipped tests, duration, coverage, and results by test group.

In plain words
What is it for?
Use it to run unit or integration tests, check coverage, watch for changes, rerun failed tests, focus on matching files, and investigate failures.
Why use it?
It makes failures easier to understand by prioritizing them, offering hints for common errors, and suggesting next commands. It also points out coverage gaps when tests pass.

Command for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the nxtg-forge plugin — 27 skills, 24 commands, 33 agents shipped together

Good fit Use it to run unit or integration tests, check coverage, watch for changes, rerun failed tests, focus on matching files, and investigate failures.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/nxtg-ai/forge-plugin/test
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/nxtg-ai/forge-plugin

Made for: Claude Code.

Or install nxtg-forge, the plugin that ships this one along with the rest of its 27 skills, 24 commands, 33 agents.

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 test

README.md
[![agentmods](https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/test/github.svg)](https://agentmods.dev/commands/nxtg-ai/forge-plugin/test)
Your own site
<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/test"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/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.

agentmods 80×15 button for test

Your own site · 80×15
<a href="https://agentmods.dev/commands/nxtg-ai/forge-plugin/test"><img src="https://agentmods.dev/badge/commands/nxtg-ai/forge-plugin/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 894 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.00008 $0.00894
Opus 5.5 $0.00003 $0.00358
Sonnet 5.5 $0.00002 $0.00179
Haiku 4.5 $0.00001 $0.00089

Measured 12d ago against content hash 6e91b2b1c7a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 12d 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.

plugins/nxtg-forge/commands/test.md · 158 lines

How it starts

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

NXTG-Forge Test Runner

You are the Test Runner - execute the project's test suite and provide detailed, actionable results.

Parse Arguments

Arguments received: $ARGUMENTS

Options:

  • No arguments: Run full test suite
  • --unit: Run only unit tests
  • --integration: Run only integration tests
  • --coverage: Run with coverage reporting
  • --watch: Run in watch mode
  • --file <pattern>: Run tests matching pattern (e.g., --file pty-bridge)
  • --failed: Re-run only previously failed tests
  • --verbose: Show full test output

Execution

Step 1: Pre-flight Check

Verify test infrastructure:

# Check if vitest is available
npx vitest --version 2>/dev/null

If vitest is not found, inform user and suggest npm install.

Step 2: Run Tests

Based on arguments, construct the vitest command:

Full suite (default):

npx vitest run --reporter=verbose 2>&1

With coverage:

npx vitest run --coverage --reporter=verbose 2>&1

Specific file pattern:

npx vitest run --reporter=verbose "<pattern>" 2>&1

Watch mode:

npx vitest --reporter=verbose 2>&1

Step 3: Parse and Display Results

After tests complete, display structured results:

NXTG-Forge Test Results
========================

SUMMARY
  Total:    {total}
  Passed:   {passed}
  Failed:   {failed}
  Skipped:  {skipped}
  Duration: {duration}

{if failed > 0}
FAILURES
  {test_file}:{test_name}
    Expected: {expected}
    Received: {received}
    Location: {file}:{line}

{/if}

{if coverage}
COVERAGE
  Statements: {stmt}%
  Branches:   {branch}%
  Functions:  {func}%
  Lines:      {lines}%

  Uncovered files:
    {file}: {uncovered_lines}
{/if}

TEST SUITES
  {suite_name}: {passed}/{total} ({duration})
  {suite_name}: {passed}/{total} ({duration})
  ...

Step 4: Analysis and Recommendations

After showing results, provide analysis:

If all tests pass:

All tests passing. Test health is good.

Suggestions:
  - Consider adding tests for uncovered files (use /nxtg-forge:gap-analysis --scope testing)
  - Current test file count: {count}

Read the full file on GitHub · 158 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. 12d ago Changed 6e91b2b1c7a6
  2. 1mo ago Changed · +32 lines · +8 tokens per session 6736f35207e6
  3. 1mo ago First seen · 126 lines · 0 tokens per session scan A 9571c3a2d72d

Subscribe to this mod's changes

test is a command published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 894 once invoked, about $0.0000 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-31.