tester

A testing specialist that checks code with unit tests, integration tests, and end-to-end tests. Unit tests check small pieces, integration tests check components working together, and end-to-end tests check complete user flows.

In plain words
What is it for?
It helps write tests, test APIs and databases, automate browser flows, check different browsers, and plan tests according to risk.
Why use it?
It helps catch broken behavior, edge cases, and regressions before code is released.

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/nth5693/gemini-kit/tester
Clone the repo
git clone --depth 1 https://github.com/nth5693/gemini-kit
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,538 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.00009 $0.01538
Opus 5 $0.00005 $0.00769
Sonnet 5 $0.00002 $0.00308
Haiku 4.5 $0.00001 $0.00154

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

Security

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.

agents/tester.md · 279 lines

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();
  });
});

Read the full file on GitHub · 279 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. 2d ago First seen · 279 lines · 9 tokens per session scan A 68792d47a838

Subscribe to this mod's changes

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.

Related

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.

mturac/everything-openai-codex · 42 tokens

noir

テスト・品質保証の専門家。ユニットテスト、E2Eテスト、検証を担当。 丁寧で優しいが、品質には妥協しない。お嬢様口調だが芯は強い。 以下のタスクに使用すべき: 「テストコード作って」「ユニットテスト書いて」 「この機能を検証して」「動作確認して」 「バグを再現して」 例: 「phantom-antennaのanalyzer.pyのテストを作成して」 「新しいAPI機能の動作検証をして」 「Issue #23 で報告されたバグの再現テストを書いて」.

nayasuda/phantom-template · 164 tokens

ruthless-tester

Breaks code. Ensures 100% test coverage + E2E validation. No feature passes without full verification.

samibs/guardloop.dev · 0 tokens

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.

hoangatg/ai-agent-toolkit · 49 tokens

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.

adcontextprotocol/adcp · 54 tokens

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.

logancyang/obsidian-copilot · 0 tokens