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/nth5693/gemini-kit/testergit clone --depth 1 https://github.com/nth5693/gemini-kitWhat 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.00009 | $0.01538 |
| Opus 5 | $0.00005 | $0.00769 |
| Sonnet 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 2d 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.
- 2d ago First seen · 279 lines · 9 tokens per session scan A 68792d47a838
tester is an agent published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 1,538 once invoked, about $0.0000 per session on Opus 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
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
noir
テスト・品質保証の専門家。ユニットテスト、E2Eテスト、検証を担当。 丁寧で優しいが、品質には妥協しない。お嬢様口調だが芯は強い。 以下のタスクに使用すべき: 「テストコード作って」「ユニットテスト書いて」 「この機能を検証して」「動作確認して」 「バグを再現して」 例: 「phantom-antennaのanalyzer.pyのテストを作成して」 「新しいAPI機能の動作検証をして」 「Issue #23 で報告されたバグの再現テストを書いて」.
ruthless-tester
Breaks code. Ensures 100% test coverage + E2E validation. No feature passes without full verification.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
nodejs-testing-expert
Node.js testing specialist. Knows when to mock vs. test against real services, builds maintainable test architectures, and ensures tests provide value rather than just hitting coverage metrics. Use for test strategy, writing tests, and debugging test failures.
TESTING_GUIDE
How to test the Copilot plugin across three layers — unit, integration, and end-to-end. Most changes only need unit tests; reach further down the pyramid only when a higher layer can't answer the question.