testing

testing is an agent for Claude Code from nxtg-ai/forge-plugin. It costs 252 tokens per session (1,529 once invoked), scanned A, original, MIT.

A coding agent that writes and reviews automated tests for services, user-interface components, and helper functions. It detects whether a project uses Vitest, Jest, or pytest and follows the project’s existing testing style.

In plain words
What is it for?
Use it to create tests, investigate flaky tests, check coverage, and test code using Vitest, Jest, or pytest.
Why use it?
It reduces the work of starting a test suite and helps cover normal behavior, errors, and edge cases. It also checks that test doubles, called mocks, match the real interfaces used by the code.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; names the TodoWrite tool.

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

Good fit Use it to create tests, investigate flaky tests, check coverage, and test code using Vitest, Jest, or pytest.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/testing/github.svg)](https://agentmods.dev/agents/nxtg-ai/forge-plugin/testing)
Your own site
<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.

agentmods 80×15 button for testing

Your own site · 80×15
<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>
Per session 252 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,529 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.00252 $0.01529
Opus 5.5 $0.00101 $0.00612
Sonnet 5.5 $0.00050 $0.00306
Haiku 4.5 $0.00025 $0.00153

Measured 1mo ago against content hash 2c65b332a1ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

plugins/nxtg-forge/agents/testing.md · 185 lines

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);
  });
});

Read the full file on GitHub · 185 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. 1mo ago Changed · +40 lines · +252 tokens per session 2c65b332a1ae
  2. 1mo ago First seen · 145 lines · 0 tokens per session scan A 4f3591fe4ed1

Subscribe to this mod's changes

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.