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.
npx agentmods add commands/nxtg-ai/forge-plugin/testgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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 | $0.00000 | $0.01285 |
| Opus 5 | $0.00000 | $0.00642 |
| Sonnet 5 | $0.00000 | $0.00257 |
| Haiku 4.5 | $0.00000 | $0.00128 |
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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:test
Execute your project's test suite with structured result parsing, failure analysis, and actionable recommendations.
| Level | L1 Vibe Coder |
| Category | Quality & Testing |
| Syntax | /forge:test [--unit] [--integration] [--coverage] [--watch] [--file <pattern>] [--failed] [--verbose] |
What It Does
/forge:test runs your test suite and transforms raw test output into a structured, actionable report. It starts with a pre-flight check to verify your test infrastructure is available, then constructs the appropriate test command based on your arguments, executes it, and parses the results into a summary showing total/passed/failed/skipped counts, duration, coverage metrics, and per-suite breakdowns.
The real value is in the analysis layer. When tests fail, the command does not just show the error -- it prioritizes failures by severity, provides quick-fix hints based on common error patterns, and suggests next commands. When all tests pass, it identifies coverage gaps and recommends files that need tests. When no tests exist at all, it guides you toward /forge:gap-analysis --scope testing to plan your testing strategy.
Without this command, you run your test runner directly, scroll through raw output to find failures, mentally prioritize which to fix first, and separately check coverage. /forge:test packages all of that into a single structured report with clear next actions.
Syntax & Options
/forge:test [--unit] [--integration] [--coverage] [--watch] [--file <pattern>] [--failed] [--verbose]
| Option | Description |
|---|---|
--unit |
Run only unit tests |
--integration |
Run only integration tests |
--coverage |
Include coverage reporting (statements, branches, functions, lines) |
--watch |
Run in watch mode for continuous feedback during development |
--file <pattern> |
Run tests matching a file pattern (e.g., --file pty-bridge) |
--failed |
Re-run only previously failed tests |
--verbose |
Show full unabridged test output |
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.
- 2d ago First seen · 126 lines · 0 tokens per session scan A 9571c3a2d72d
test is a command published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,285 tokens. 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.
Other commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
paul:verify
Guide manual user acceptance testing of recently built features.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.