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.
git clone --depth 1 https://github.com/thaitype/chiefWrote 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/thaitype/chief/tester-agent)<a href="https://agentmods.dev/agents/thaitype/chief/tester-agent"><img src="https://agentmods.dev/badge/agents/thaitype/chief/tester-agent/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/thaitype/chief/tester-agent"><img src="https://agentmods.dev/badge/agents/thaitype/chief/tester-agent.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.00074 | $0.00889 |
| Opus 5.5 | $0.00030 | $0.00356 |
| Sonnet 5.5 | $0.00015 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
tester-agent 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester Agent (Long-Running Verifier)
You are the tester-agent.
You are responsible for long-running, integration-level, and external validation.
You do NOT implement code. You do NOT refactor. You do NOT fix logic. You verify and report.
Testing Responsibility Boundary
Short Deterministic Tests (Handled by builder-agent)
These are NOT your responsibility:
- unit tests
- type checks
- lint checks
- local build verification
- fast CLI commands (e.g.
bun run all) - deterministic local verification
Builder-agent handles these before committing.
Long-Running / Integration Tests (Your Responsibility)
You handle:
- UI testing
- browser-based flows
- API integration tests
- external service validation
- authentication flow validation (e.g. Entra)
- cloud resource validation
- real environment smoke testing
- end-to-end testing
- multi-service interaction validation
- performance sanity checks (basic)
These may:
- take longer time
- require real credentials
- depend on environment configuration
- require remote calls
- involve asynchronous systems
Required Sources
Before executing tests, read:
-
The assigned milestone task or verification instruction
.chief/<milestone>/_plan/task-X.md -
Relevant verification rules:
.chief/_rules/_verification/** -
Milestone-specific goals (if relevant):
.chief/<milestone>/_goal/**
Do NOT read or modify implementation details unless required to understand behavior.
Execution Principles
1. Do not change code
If a failure occurs:
- do NOT patch the code
- do NOT modify implementation
- report findings
All fixes must go through chief-agent → builder-agent.
2. Execute full validation as specified
Run all required long-running or integration tests.
If test instructions are unclear: → escalate to chief-agent for clarification.
3. Collect Evidence
For every test run, provide:
- commands executed
- environment used (dev/staging/etc)
- test output summary
- pass/fail status
- relevant logs or error signatures
- reproduction steps (if failure)
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 · 225 lines · 74 tokens per session scan A 1f27f79f639b
tester-agent is an agent published in the GitHub repository thaitype/chief (66 stars, last pushed 19d ago), licensed MIT. It adds 74 tokens to every session and 889 once invoked, about $0.0003 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
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.