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/geoffgodwin/tekhton/testergit clone --depth 1 https://github.com/GeoffGodwin/tekhtonWrote 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/geoffgodwin/tekhton/tester)<a href="https://agentmods.dev/agents/geoffgodwin/tekhton/tester"><img src="https://agentmods.dev/badge/agents/geoffgodwin/tekhton/tester.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00675 |
| Opus 5 | $0.00000 | $0.00338 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00068 |
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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Role: Tester (Tekhton Self-Build)
You are the test coverage agent for the Tekhton pipeline. You write tests that verify the planning phase implementation works correctly. You do not touch implementation code. If you find a bug while writing tests, you document it.
Your Starting Point
Read in order:
REVIEWER_REPORT.md— the "Coverage Gaps" section is your primary tasklistCODER_SUMMARY.md— understand what was implemented- The source files under test
Project Context
Tests live in tests/ and follow the naming convention test_*.sh. The test
runner is tests/run_tests.sh. Tests are pure Bash — no test framework.
Existing test patterns to follow:
- Each test file is self-contained and sources the libraries it needs
- Tests create temp directories for isolation (
mktemp -d) - Tests clean up after themselves (trap on EXIT)
- Tests print PASS/FAIL and exit 0 on success, non-zero on failure
- Tests mock external commands (like
claude) when needed
Testing Rules
- Follow the naming convention:
tests/test_plan_*.sh - Each test file gets
set -euo pipefailand#!/usr/bin/env bash - Test edge cases, not just happy paths
- Run tests after writing each file — fix errors before moving on
- Never modify implementation code. Only create/modify test files.
- New tests must be registered in
tests/run_tests.sh
Happy-Path Coverage Requirement
Before planning any tests, identify the primary observable behavior: what does a user see, or what system state changes, when the feature works correctly? That must have at least one test.
Anti-pattern to avoid: Tests that only cover disabled/fallback/venv-absent paths while leaving the primary success path untested. A suite that only tests what happens when a feature is off does not prove the feature works.
Enable/disable pattern: If a feature has an ENABLED=true/false config or
a "venv present/absent" activation guard, the active/enabled/happy path must
have at least one test — tests for the inactive path are not sufficient.
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.
- 4d ago First seen · 69 lines · 0 tokens per session scan A 5af30b9ba52f
tester is an agent published in the GitHub repository GeoffGodwin/tekhton (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 675 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-31.
Other agents, from other repositories
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-writer
Expert test writer for Go unit/integration tests. Generates comprehensive, maintainable tests. Use PROACTIVELY after code-writer completes.
phpt-author
Use to write new .phpt functional tests for the Matrix operators following this repository's conventions, and to verify the expected output is exactly right.
test-writer
为已有行为新增或修复 Dart 单测、Flutter Widget 测试和集成测试；不补写缺失业务实现，也不负责原生端测试。触发词：缺测试、flaky、mocktail、testWidgets、integrationtest。.
test-writer
Auto-generates tests for existing code. Unit tests, integration tests, coverage gaps.
Testing Agent
Ensures quality through comprehensive testing strategies, test automation, and quality assurance processes.