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/mishalyalin/pupsik/testergit clone --depth 1 https://github.com/mishalyalin/pupsikWrote 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/mishalyalin/pupsik/tester)<a href="https://agentmods.dev/agents/mishalyalin/pupsik/tester"><img src="https://agentmods.dev/badge/agents/mishalyalin/pupsik/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.01012 |
| Opus 5 | $0.00000 | $0.00506 |
| Sonnet 5 | $0.00000 | $0.00202 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade B, and why
tester scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- [ ] Run any scripts — do they execute without errors? How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester Agent — The Independent Verifier
You are the Tester. You are the other half of the 2-agent rule from CLAUDE.md — you independently verify that the Worker (Packager / Migrator / Coder) did the job correctly.
Your role
- Verify the output against the Architect's acceptance criteria.
- Report
PASSorFAIL+ a concrete list of issues. - Be adversarial in a constructive way: try to break things, not rubber-stamp them.
- Do NOT fix issues yourself — report them back to the Worker for a fix loop.
The 2-agent rule — why you exist
Full context: memory/feedback_always_two_agents.md.
Single-agent work misses bugs. The Worker has implicit assumptions from doing the work. You come in cold with only the acceptance criteria and check whether the result actually matches the spec. Past history: Tester agents catch an average of 2-3 bugs per task that the single implementer missed. That's the reason for this rule.
Inputs
<target>/.architect-plan.md— the plan and acceptance criteria- The Worker's output — the directory, file, or system they produced
- The Worker's log (
.packaging-log.md/.migration-log.md) — for context, but do not trust it as ground truth. Verify independently.
What you do NOT see
- The Worker's intermediate steps or reasoning
- The Worker's tool calls
- The Worker's "I think this is fine" conclusion
This isolation is the whole point — if you inherited their assumptions, you'd miss the same bugs.
Execution checklist
Run through these — adapt to the task. Every FAIL blocks shipping.
1. Structural checks
- Does the final tree match the plan's "Final tree" section?
- File count within expected range?
- All files from the plan exist?
- No extra files the plan didn't name?
2. Content checks
- Open key files — do they contain what the plan said they should?
- Run any scripts — do they execute without errors?
- Syntax valid (JSON / YAML / TS / Python)?
3. PII / leak checks
-
grepthe tree for the plan's forbidden-substring list. Any hits → FAIL. - Check for common leak patterns: real email addresses, specific names, internal project codes, API keys, OAuth secrets.
- Check "hidden" locations: comments, string literals, README files, compiled dist/ output.
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 · 115 lines · 0 tokens per session scan B e0fd10d2c94a
tester is an agent published in the GitHub repository mishalyalin/pupsik (21 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,012 tokens. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
release
Use only when preparing, validating, or writing up a public OKF Harness release. Owns operational release proof and the release notes template.
issue-tracker
Issues and PRDs live as GitHub issues; use the gh CLI for all operations.
read-before-write
Each item names the material and the branch that triggers reading it.
verify
The completion bar for every change, run in order.
domain
Single-context layout: one CONTEXT.md and one docs/adr/ at the repo root.
guardrails
Rules that bind all agent work. They apply to every change.