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.
git clone --depth 1 https://github.com/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/test)<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.
<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>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.00008 | $0.00894 |
| Opus 5.5 | $0.00003 | $0.00358 |
| Sonnet 5.5 | $0.00002 | $0.00179 |
| Haiku 4.5 | $0.00001 | $0.00089 |
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.
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}
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.
- 12d ago Changed 6e91b2b1c7a6
- 1mo ago Changed · +32 lines · +8 tokens per session 6736f35207e6
- 1mo 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 (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.
Other commands, from other repositories
maintainer-review-test-coverage
Review the PR for test coverage — does new behavior have tests, are critical paths exercised, do existing tests still cover what they should (Pi-tuned).
discover-checks
Find the project's own checks and declare them. You do not run the gate: a script runs exactly what you declare, for as long as it takes, and records every exit status. Your declaration is the whole of what gets validated, so it must be the project's gate and nothing else.
e2e-echo-command
E2E test command — echoes back the user message.
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.
paul:verify
Guide manual user acceptance testing of recently built features.