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 agents/nxtg-ai/forge-plugin/testinggit 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.02046 |
| Opus 5 | $0.00000 | $0.01023 |
| Sonnet 5 | $0.00000 | $0.00409 |
| Haiku 4.5 | $0.00000 | $0.00205 |
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 yesterday.
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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing
Generates comprehensive test suites, diagnoses flaky tests, and enforces coverage standards -- with enforcement rules that catch the bugs "all tests pass" misses.
| Level | L1 Vibe Coder |
| Category | Domain Specialist |
| Model | Sonnet |
What It Does
The Testing agent writes tests so you do not have to start from scratch. Hand it a new service class, React component, or utility function, and it generates tests covering happy paths, error cases, and edge cases with properly shaped mocks. It detects your testing framework (Vitest, Jest, pytest) and generates tests that match your existing patterns -- same import style, same assertion library, same file naming convention.
What elevates this agent beyond "generate a test" is its enforcement rules. MOCK_SHAPE_SYNC ensures that every mock object matches the actual production code's usage patterns. If your service accesses this.api.interceptors.request.use(), the Testing agent verifies the mock has interceptors.request.use as a callable function. This catches the class of bug where tests pass because they test a mock, not the real interface. TYPECHECK_ZERO_TOLERANCE ensures generated tests compile cleanly -- no implicit any on callback parameters, no missing properties on mock types. AUTH_E2E_GUARD ensures end-to-end tests for protected routes include authentication setup.
The Testing agent also diagnoses flaky tests. It identifies the three common causes -- timing issues (async race conditions, missing await), order dependence (shared mutable state between tests), and external dependence (network calls, file system, time-of-day) -- and applies targeted fixes. For timing issues, it adds proper async/await and fake timers. For order dependence, it isolates state in beforeEach. For external dependence, it introduces mocks with proper cleanup.
When to Use It
- After writing new code: When you have implemented a service, component, or module and need tests generated from its public API surface.
- When coverage is below target: When you need to close coverage gaps and want the Testing agent to identify untested files and generate tests for them, prioritized by criticality.
- When tests are flaky: When tests pass sometimes and fail other times, and you need systematic diagnosis and fixes rather than trial-and-error.
- When setting up test infrastructure: When a project needs testing configured from scratch -- framework setup, config files, CI integration, test utilities.
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.
- yesterday First seen · 145 lines · 0 tokens per session scan A 4f3591fe4ed1
testing is an agent 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 2,046 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 agents, from other repositories
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
emulate-engineer
Stateful API emulation via Vercel emulate. Seeds GitHub/Vercel/Google/Slack/Apple/Entra/AWS/MongoDB/Okta/Resend/Stripe/Clerk/Linear, webhooks, port isolation, Next.js adapter. Use to replace flaky API mocks.
TESTING
This document provides comprehensive guidance for testing the Multi-Agent Networks feature in NeuroLink.