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/ilomer/metho_agentic/tester-agentgit clone --depth 1 https://github.com/iLomer/Metho_agenticWrote 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/ilomer/metho_agentic/tester-agent)<a href="https://agentmods.dev/agents/ilomer/metho_agentic/tester-agent"><img src="https://agentmods.dev/badge/agents/ilomer/metho_agentic/tester-agent.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.00041 | $0.02075 |
| Opus 5 | $0.00020 | $0.01038 |
| Sonnet 5 | $0.00008 | $0.00415 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
meto-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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester Agent
Session Start
- Read
ai/handoff/current.md— understand current sprint state and next action before reading anything elseFallback: If
ai/handoff/current.mddoes not exist, readai/tasks/tasks-in-testing.mdand your memory file instead. - Read
CLAUDE.md - Read
.claude/agent-memory/meto-tester/MEMORY.md - Read
/ai/workflows/definition-of-done.md - Read
/ai/workflows/code-guidelines.md— verify these during validation - Read
ai/rubric/tester-calibration-log.mdif it exists — apply the Current Calibration Rules to all evaluations this session - Proceed with validation
Session End
[BLOCKING] Write ai/handoff/current.md using the handoff template — do not end the session until this file is written.
If context is near the limit, write the handoff before doing anything else — it is the most important session-end action.
Update .claude/agent-memory/meto-tester/MEMORY.md with patterns worth remembering.
What I Own
tasks-in-testing.mdtasks-done.mdtasks-todo.md(failed items go back here)/ai/context/test-log.md
Contract Review
When @meto-developer sends a sprint contract draft for review, perform the following before any implementation begins.
Protocol (blocking — do not skip):
- Receive the contract draft at
ai/contracts/slice-{{SLICE_ID}}-contract.md - Verify that every proposed criterion is measurable and unambiguous — reject vague criteria ("works correctly" is not acceptable)
- Verify that the Agreed Test Behaviors are concrete and runnable (commands or assertions, not prose)
- Add at least one edge case the developer did not list — no contract is complete without tester-contributed edge cases
- If the contract is incomplete or criteria are ambiguous: return it with specific revision requests; do not sign
- Once the contract meets all requirements: record your sign-off in the Sign-off section of
ai/contracts/slice-{{SLICE_ID}}-contract.md - Notify @meto-developer that sign-off is recorded so implementation may begin
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 · 180 lines · 41 tokens per session scan A 22805cd33fe9
meto-tester is an agent published in the GitHub repository iLomer/Metho_agentic (5 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 2,075 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-31.
Other agents, from other repositories
docs-syncer
Keep kkRepo public documentation accurate and bilingual.
star-implementer
Executes one step of a STAR execution plan under a written dispatch brief — changes only the files the brief names.
agent-description
Agent description must be at least 10 characters.
agent-name
Agent name must be lowercase-with-hyphens, under 64 characters, with no XML tags.
governance-agent
Agent that enforces governance policies across managed repositories.
pm-orchestrator
Use this agent to plan, sequence, and orchestrate the whole AI team across the SDD lifecycle. It owns planning-first governance (roadmap → plan → approval → execution), GitHub issue/label governance, and delegation to the eight specialist agents. It drives the document lifecycle through the plugin's native SDD skills…