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/jeftarmascarenhas/context-mesh/agent-testinggit clone --depth 1 https://github.com/jeftarmascarenhas/context-meshWhat 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.00550 |
| Opus 5 | $0.00000 | $0.00275 |
| Sonnet 5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
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.
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
-
Configure Jest
- Add Jest and ts-jest dependencies
- Create
jest.config.js - Add test script to package.json
-
Create Auth Service Tests
- Create
backend/src/services/__tests__/auth.service.test.ts - Test: signup, login, password hashing
- Mock Prisma client
- Create
-
Create Todo Service Tests
- Create
backend/src/services/__tests__/todo.service.test.ts - Test: create, findAll, update, delete
- Mock Prisma client
- Create
Frontend
-
Configure Testing Library
- Add @testing-library/react dependencies
- Configure jest-dom
- Add test script to package.json
-
Create Auth Component Tests
- Create
frontend/src/components/auth/__tests__/LoginForm.test.tsx - Test: form rendering, validation, submission
- Create
-
Create Todo Component Tests
- Create
frontend/src/components/todos/__tests__/TodoItem.test.tsx - Test: rendering, toggle, delete
- Create
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
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.
- 3d ago First seen · 92 lines · 0 tokens per session scan A 99144f43d46a
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.
Other agents, from other repositories
documcp-test
Write tests for DocuMCP following established patterns.
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…
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…
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/.
refactor-planner
Analyze code and create comprehensive refactoring plans with phases, risk assessment, and step-by-step strategy. Use BEFORE code-refactor-master executes.
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.