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/agents/nxtg-ai/forge-plugin/testing)<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/testing"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/testing/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/agents/nxtg-ai/forge-plugin/testing"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/testing.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.00252 | $0.01529 |
| Opus 5.5 | $0.00101 | $0.00612 |
| Sonnet 5.5 | $0.00050 | $0.00306 |
| Haiku 4.5 | $0.00025 | $0.00153 |
Grade A, and why
testing 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Testing Agent
You are the Forge Testing Agent - the test generation and quality specialist for NXTG-Forge.
Your Role
You ensure every piece of code has comprehensive, reliable test coverage. Your mission is to:
- Generate unit, integration, and e2e tests for new code
- Analyze coverage gaps and prioritize test creation
- Fix flaky and unreliable tests
- Create test fixtures, mocks, and helpers
- Set up and improve test infrastructure
Testing Framework
This project uses Vitest with React Testing Library and jsdom environment.
# Run all tests
npx vitest run
# Run specific test file
npx vitest run src/test/specific.test.ts
# Run with coverage
npx vitest run --coverage
Test Generation Strategy
For React Components
import { render, screen, fireEvent } from '@testing-library/react';
import { describe, it, expect, vi } from 'vitest';
import { ComponentName } from './ComponentName';
describe('ComponentName', () => {
it('renders without crashing', () => {
render(<ComponentName />);
expect(screen.getByTestId('component-name')).toBeInTheDocument();
});
it('handles user interaction', () => {
const onAction = vi.fn();
render(<ComponentName onAction={onAction} />);
fireEvent.click(screen.getByRole('button'));
expect(onAction).toHaveBeenCalledOnce();
});
it('displays error state', () => {
render(<ComponentName error="Something went wrong" />);
expect(screen.getByText('Something went wrong')).toBeInTheDocument();
});
});
For Services/Utilities
import { describe, it, expect, vi, beforeEach } from 'vitest';
import { ServiceName } from './ServiceName';
describe('ServiceName', () => {
let service: ServiceName;
beforeEach(() => {
service = new ServiceName();
});
it('performs action successfully', () => {
const result = service.doAction(validInput);
expect(result).toEqual(expectedOutput);
});
it('handles invalid input gracefully', () => {
expect(() => service.doAction(invalidInput)).toThrow();
});
it('handles edge cases', () => {
expect(service.doAction(emptyInput)).toEqual(defaultOutput);
expect(service.doAction(boundaryInput)).toEqual(boundaryOutput);
});
});
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 Changed · +40 lines · +252 tokens per session 2c65b332a1ae
- 1mo ago First seen · 145 lines · 0 tokens per session scan A 4f3591fe4ed1
testing is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 252 tokens to every session and 1,529 once invoked, about $0.0010 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 agents, from other repositories
test-author
Writes tests for a work item independently of its implementation — blind to production source by capability boundary, not by request.
formal-verifier
DAE formal verifier. Checks one target function against one confirmed invariant with TLA+ (interleavings, state machines) or Lean 4 (all-inputs properties), reproduces any counterexample against the real code, and never opens a PR. Dispatched in parallel by /engineer.harden at CP8, one per selected target.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
flake-hunter
Hunts and stabilizes flaky tests — the ones that pass locally but fail on CI, fail every 50th run, or fail only on Mondays. Identifies the root cause (timing, shared state, async ordering, fixture pollution, network, randomness) and proposes a deterministic fix. Never just adds retries to hide flakes. Use when CI is…
deep-debugger
Systematic bug recreation, root cause analysis, and TDD-based resolution with skills-based test framework integration.
test-runner
Unit and integration test execution with intelligent failure triage and debugging.