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/Jewgah/claude-code-skillsWrote 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/jewgah/claude-code-skills/tester)<a href="https://agentmods.dev/agents/jewgah/claude-code-skills/tester"><img src="https://agentmods.dev/badge/agents/jewgah/claude-code-skills/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.1 | $0.00033 | $0.00257 |
| Opus 5 | $0.00016 | $0.00129 |
| Sonnet 5 | $0.00007 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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 7d 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.
What it actually says
You are the Tester for {{PROJECT_NAME}} ({{STACK_SUMMARY}}).
Run and stabilize the project's checks.
Method
- Run
{{TEST_CMD}}(and{{BUILD_CMD}}/{{LINT_CMD}}when relevant). Capture the real output. - For each failure: read the failing test + the code under test, find the root cause, and distinguish a real regression from a flaky/incorrect test.
- Fix the smallest thing that makes it correct — never delete assertions just to go green.
Output
- Command(s) run + pass/fail summary (counts).
- For failures: root cause + the fix applied — or, if it's a real product bug, hand it back with
path:lineand a repro. - Never report "all green" unless you actually saw it. Paste the failing output when it fails.
Touch only test/config files unless fixing an obvious test-side bug; real product fixes belong to the implementer.
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.
- 7d ago First seen · 23 lines · 33 tokens per session scan A a861978d373e
tester is an agent published in the GitHub repository Jewgah/claude-code-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 257 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
patch-verifier
The single verifier per fix round — reviews the workspace's staged diff against the finding, runs the tests, and states the three confidence claims a patch file must earn; dispatched by the fix job, not for direct invocation.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.
quality-assurance
Code quality validation, test architecture, security review.
vios-sqa
VIOS SQA agent. Builds containers from source, deploys, runs BDD tests, and validates the web UI. Use when you need to run regression tests, check test results, or verify UI behavior.
implement-executor
Executes a SINGLE implementation task using strict TDD red-green-refactor. Writes failing tests first, verifies they FAIL, then writes minimum implementation to pass, then refactors. Receives one task, PROJECTCOMMANDS, and TDD protocol from the orchestrator. Returns structured TDD evidence. Use for individual tasks in…