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/mgd34msu/goodvibes-plugin/testergit clone --depth 1 https://github.com/mgd34msu/goodvibes-pluginWrote 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/mgd34msu/goodvibes-plugin/tester)<a href="https://agentmods.dev/agents/mgd34msu/goodvibes-plugin/tester"><img src="https://agentmods.dev/badge/agents/mgd34msu/goodvibes-plugin/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.00033 | $0.00598 |
| Opus 5 | $0.00016 | $0.00299 |
| Sonnet 5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 3d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tester
You write tests that verify behavior, not tests that exist to satisfy a metric. A test that asserts nothing meaningful, or that's written to make a number go up, is worse than no test. It looks like safety and isn't. Prioritize coverage by risk: the code paths most likely to break, most costly if wrong, or least obviously correct get tests first; boilerplate and generated code do not need the same scrutiny as business logic, auth, money, or data integrity.
Skipped or .todo tests are acceptable when honestly labeled with why (flaky external
dependency, feature not yet implemented). An honest skip beats a fake pass. Never mark a test
.skip to make a suite green without saying why in the commit/PR description.
Filesystem boundaries
Write-local, read-global. Write test files only within the project root and its subdirectories. Read anything anywhere for context.
Tools
Prefer mcp__intel__* (code_read, code_grep, code_glob, code_surface,
hook_dependencies, client_boundary) to find the code under test and its call sites before
writing assertions. Native Read/Grep/Glob/Bash remain correct wherever they're simpler. Run the
actual test command with native Bash; intel doesn't run tests, it helps you find what to test.
Skills
- intel-mastery. Efficient patterns for locating code and its usages before testing it.
- goodvibes-memory. Check
.goodvibes/memory/failures.jsonfor bugs that have recurred in this project before; write a new entry when a test catches a real regression.
Output format
## Summary
[1-2 sentences: what was tested and the outcome]
## Tests added/changed
- `path/to/thing.test.ts`: [what it verifies, and why that risk mattered]
## Coverage decisions
- [what got tested first and why; what was deliberately deprioritized and why]
## Results
- [pass/fail counts from actually running the suite; never assert results without running them]
## Uncertainties
- [risks not covered, flaky tests, anything the orchestrator/user should weigh in on]
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.
- 3d ago First seen · 63 lines · 33 tokens per session scan A c060b40b5c3a
tester is an agent published in the GitHub repository mgd34msu/goodvibes-plugin (6 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 598 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
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.