agent-testing

A testing agent that creates unit tests for backend services and frontend components. Unit tests check small parts of an application separately; Jest runs the tests and React Testing Library checks user-interface behavior.

In plain words
What is it for?
Use it to configure Jest, add backend service tests, and test React login components. The listed checks include signup, login, password hashing, todo creation and editing, and form behavior.
Why use it?
It adds test coverage without changing the application logic. This helps catch errors in authentication, todo operations, forms, validation, and submissions.

Agent

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.

agentmods
npx agentmods add agents/jeftarmascarenhas/context-mesh/agent-testing
Clone the repo
git clone --depth 1 https://github.com/jeftarmascarenhas/context-mesh
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 550 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00550
Opus 5 $0.00000 $0.00275
Sonnet 5 $0.00000 $0.00110
Haiku 4.5 $0.00000 $0.00055

Measured 3d ago against content hash 99144f43d46a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-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 3d 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.

examples/todo-app-complete/context/agents/agent-testing.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent: Testing - Todo App

Purpose

Implement unit tests for backend services and frontend components with Jest and React Testing Library.

Context Files to Load

  • @context/intent/feature-testing.md
  • @context/decisions/005-testing-strategy.md
  • @context/knowledge/patterns/testing.md

Scope

  • Allowed: backend/src/, frontend/src/, test config files
  • Prohibited: Modify application logic

Execution Steps

Backend

  1. Configure Jest

    • Add Jest and ts-jest dependencies
    • Create jest.config.js
    • Add test script to package.json
  2. Create Auth Service Tests

    • Create backend/src/services/__tests__/auth.service.test.ts
    • Test: signup, login, password hashing
    • Mock Prisma client
  3. Create Todo Service Tests

    • Create backend/src/services/__tests__/todo.service.test.ts
    • Test: create, findAll, update, delete
    • Mock Prisma client

Frontend

  1. Configure Testing Library

    • Add @testing-library/react dependencies
    • Configure jest-dom
    • Add test script to package.json
  2. Create Auth Component Tests

    • Create frontend/src/components/auth/__tests__/LoginForm.test.tsx
    • Test: form rendering, validation, submission
  3. Create Todo Component Tests

    • Create frontend/src/components/todos/__tests__/TodoItem.test.tsx
    • Test: rendering, toggle, delete

Expected Test Structure

backend/src/
└── services/
    └── __tests__/
        ├── auth.service.test.ts
        └── todo.service.test.ts

frontend/src/
└── components/
    ├── auth/
    │   └── __tests__/
    │       └── LoginForm.test.tsx
    └── todos/
        └── __tests__/
            └── TodoItem.test.tsx

Definition of Done

  • Jest configured for backend
  • React Testing Library configured for frontend
  • Auth service tests pass
  • Todo service tests pass
  • Component tests pass
  • Coverage > 70%

Verification

# Backend tests
cd backend
pnpm test
pnpm test -- --coverage

# Frontend tests
cd frontend
pnpm test
pnpm test -- --coverage

Read the full file on GitHub · 92 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. 3d ago First seen · 92 lines · 0 tokens per session scan A 99144f43d46a

Subscribe to this mod's changes

agent-testing is an agent published in the GitHub repository jeftarmascarenhas/context-mesh (39 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 550 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-30.

Related

Other agents, from other repositories

documcp-test

Write tests for DocuMCP following established patterns.

tosin2013/documcp · 15 tokens

test-author

Writes and maintains the repo's unit tests when a feature changes. Optimizes for catching real business-logic regressions, not coverage count — every test must name the regression it would catch or it does not get written. Use AFTER implementing a feature/fix and BEFORE /verify-done. Examples — "write tests for the…

SeanningTatum/cf-saas-starter-react-router · 105 tokens

automation-qa-engineer

Writes automated test suites following the Testing Pyramid (70% unit, 20% integration, 10% E2E). Enforces code quality standards (linting, coverage, SAST, SCA). Implements CI-wired test runners and quality gates. Detects flaky tests and ensures hermetic test isolation. Use when the user asks to build test suites…

saitarrun/Sdlc-ai-workflow · 94 tokens

ring:qa

Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.

LerianStudio/ring · 52 tokens

refactor-planner

Analyze code and create comprehensive refactoring plans with phases, risk assessment, and step-by-step strategy. Use BEFORE code-refactor-master executes.

aspenkit/aspens · 33 tokens

testing-strategies-prompt

You are a testing specialist agent. Your mission: design and implement comprehensive testing strategies, ensure code quality through systematic testing, and guide test-driven development practices.

Rtur2003/Claude-Code-Promts-Skills · 0 tokens