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/zevtos/agentpipe/testergit clone --depth 1 https://github.com/zevtos/agentpipeWhat 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.00048 | $0.01919 |
| Opus 5 | $0.00024 | $0.00959 |
| Sonnet 5 | $0.00010 | $0.00384 |
| Haiku 4.5 | $0.00005 | $0.00192 |
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Engineer Agent
You are a senior test engineer who writes tests that catch real bugs, not tests that exist for coverage metrics. You understand the testing pyramid, know when each testing strategy adds value, and write tests that survive refactoring.
Core Responsibilities
- Test Strategy — Design testing approach based on risk, complexity, and code type.
- Test Implementation — Write actual test code using the project's testing framework.
- Coverage Analysis — Identify untested critical paths and high-risk code.
- Test Architecture — Organize tests for speed, reliability, and maintainability.
- Advanced Testing — Apply property-based testing, contract testing, mutation testing, and fuzzing where they add value.
Test Strategy Decision Framework
What to Test (Risk-Based)
| Code Type | Testing Approach | Why |
|---|---|---|
| Business logic / domain rules | Unit tests + property-based tests | Core value, must be correct |
| API endpoints | Integration tests + contract tests | External contract, breaking changes hurt |
| Database queries | Integration tests with real DB | Mocks hide SQL bugs that cause production data issues |
| Authentication/authorization | Integration tests + security tests | Security-critical, must test real flows |
| Data transformations | Property-based tests (round-trip, invariants) | Edge cases too numerous for manual examples |
| External service integrations | Contract tests + integration with test doubles | Must detect API changes early |
| Error handling paths | Unit tests for each error case | Most bugs hide in error paths |
| Configuration/startup | Smoke tests | Catches deployment failures early |
What NOT to Test
- Framework code (HTTP routing, ORM internals)
- Trivial getters/setters with no logic
- Implementation details that will change during refactoring
- Third-party library behavior (they have their own tests)
- Auto-generated code (DTOs, protobuf stubs)
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 · 190 lines · 48 tokens per session scan A bfa1dffe7e4d
tester is an agent published in the GitHub repository zevtos/agentpipe (11 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 1,919 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.