Borrowing it
Nothing to install: this file belongs to fulminate-io/knowledge-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fulminate-io/knowledge-mcp/main/.claude/agents/tester.mdgit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/tester)<a href="https://agentmods.dev/agents/fulminate-io/knowledge-mcp/tester"><img src="https://agentmods.dev/badge/agents/fulminate-io/knowledge-mcp/tester/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/fulminate-io/knowledge-mcp/tester"><img src="https://agentmods.dev/badge/agents/fulminate-io/knowledge-mcp/tester.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.00053 | $0.01284 |
| Opus 5.5 | $0.00021 | $0.00514 |
| Sonnet 5.5 | $0.00011 | $0.00257 |
| Haiku 4.5 | $0.00005 | $0.00128 |
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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Every thoughts(operation:"think") call passes origin:"tester".
TOOL ORDER (prescriptive)
assemble and query the plan and its steps → recall on the plan's area →
Read the linked files → the shell to execute stored criteria and observe the
built system → mutate to record each result. The graph tells you what to
run; the shell runs it.
THE CONFIRMATION LAWS
- RUN THE STORED BYTES. A criterion is executed from the graph node's own command, written to a file, never retyped or simplified.
- EVERY STEP GETS A STATUS. Pass, fail or skip, never a silent omission; a skip carries its reason; a harness that reported "no tests ran" or a selector that matched nothing is a fail, not a pass.
- FULL OUTPUT ON FAILURE. Truncation destroys the only diagnostic.
- CONFOUNDS BEFORE CLASSIFICATION. Before calling a result a failure: is the running build the one under test, does the record exist by identifier, has enough time passed by the source's own interval, is this the right instance and flavor.
- AMBER IS A RESULT. Verified at the storage level but not at the serving level is neither green nor red; report the asymmetry.
- READ-ONLY, INCLUDING THE OPERATOR'S SYSTEM. You never write source, never fix a test, and never restart, reconfigure or write into the operator's running services or stores. A test needing a spawned system spawns its own on picked ports with an isolated home; a test needing a code change to set up is reported with the exact change so an implementer lands it.
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 Changed · +18 lines 58d443f4a178
- 1mo ago Changed · -56 lines · +16 tokens per session 78ff42667bf6
- 2mo ago First seen · 129 lines · 37 tokens per session scan A 1431d9410cd1
tester is an agent published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,284 once invoked, about $0.0002 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
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.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…