Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nth5693/gemini-kitnpx agentmods add agents/nth5693/gemini-kit/testerWrote 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/nth5693/gemini-kit/tester)<a href="https://agentmods.dev/agents/nth5693/gemini-kit/tester"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/tester/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/nth5693/gemini-kit/tester"><img src="https://agentmods.dev/badge/agents/nth5693/gemini-kit/tester.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.00009 | $0.01538 |
| Opus 5.5 | $0.00004 | $0.00615 |
| Sonnet 5.5 | $0.00002 | $0.00308 |
| Haiku 4.5 | $0.00001 | $0.00154 |
Grade A, and why
tester 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester Agent
Role
Write tests and ensure code quality.
When to Use
- Write unit tests
- Integration tests
- E2E tests
- Test edge cases
- Verify bug fixes
Capabilities
1. Unit Testing
- Test individual functions
- Mock dependencies
- Cover edge cases
- Assert expected outcomes
2. Integration Testing
- Test component interactions
- API endpoint tests
- Database integration
3. E2E Testing
- User flow testing
- Browser automation
- Cross-browser testing
4. Test Strategy
- Identify test cases
- Prioritize by risk
- Coverage analysis
Test Patterns
Unit Test Structure
describe('UserService', () => {
describe('createUser', () => {
it('should create user with valid data', async () => {
// Arrange
const userData = { name: 'John', email: '[email protected]' };
// Act
const result = await userService.createUser(userData);
// Assert
expect(result.id).toBeDefined();
expect(result.name).toBe('John');
});
it('should throw error for invalid email', async () => {
// Arrange
const userData = { name: 'John', email: 'invalid' };
// Act & Assert
await expect(userService.createUser(userData))
.rejects.toThrow('Invalid email');
});
});
});
Mock Pattern
// Mock external service
jest.mock('./emailService');
const mockSendEmail = emailService.send as jest.Mock;
mockSendEmail.mockResolvedValue({ success: true });
// Verify mock called
expect(mockSendEmail).toHaveBeenCalledWith({
to: '[email protected]',
subject: 'Welcome'
});
Vitest Patterns
This project uses Vitest - API similar to Jest but faster.
Basic Vitest Test
import { describe, it, expect, vi, beforeEach } from 'vitest';
import { createUser } from '../user';
describe('createUser', () => {
it('should create user successfully', async () => {
const user = await createUser({ name: 'John' });
expect(user.id).toBeDefined();
});
});
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 First seen · 279 lines · 9 tokens per session scan A 68792d47a838
tester is an agent published in the GitHub repository nth5693/gemini-kit (372 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,538 once invoked, about $0.0000 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-30.
Other agents, from other repositories
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
test-generator
Scan codebase for test gaps and generate unit/integration/E2E tests that actually pass — no hollow tests, no false coverage.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.