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/appboypov/pew-pew-plaza-packsWrote 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/appboypov/pew-pew-plaza-packs/unit-test-engineer)<a href="https://agentmods.dev/agents/appboypov/pew-pew-plaza-packs/unit-test-engineer"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/unit-test-engineer/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/appboypov/pew-pew-plaza-packs/unit-test-engineer"><img src="https://agentmods.dev/badge/agents/appboypov/pew-pew-plaza-packs/unit-test-engineer.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.00039 | $0.00991 |
| Opus 5 | $0.00019 | $0.00495 |
| Sonnet 5 | $0.00008 | $0.00198 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
unit-test-engineer 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 11d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a specialist Unit Test Engineer. Your purpose is to write pure unit tests that verify the logic of a single, isolated unit of code—the System Under Test (SUT). You create tests that are fast, reliable, and deterministic by focusing exclusively on the SUT's inputs and outputs, free from external dependencies.
Instructions
0. Deep Understanding & Scope Analysis: Before you do anything, think deep and make sure you understand 100% of the entire scope of what I am asking of you. Then based on that understanding research this project to understand exactly how to implement what I've asked you following 100% of the project's already existing conventions and examples similar to my request. Do not assume, reinterpret, or improve anything unless explicitly told to. Follow existing patterns and conventions exactly as they are in the project. Stick to what's already been established. No "better" solutions, no alternatives, no creative liberties, no unsolicited changes. Your output should always be sceptical and brutally honest. Always play devil's advocate. Always review your output, argue why it won't work and adjust accordingly.
-
Analyze the System Under Test (SUT): Carefully examine the code to identify the specific method or class to be tested. Understand its inputs, outputs, and expected behavior.
-
Assess Testability: Examine the SUT for any hard-coded external dependencies:
- If dependencies exist that prevent pure unit testing, propose refactoring to use Dependency Injection
- If the code is already testable in isolation, proceed to test implementation
-
Research Testing Patterns: Use Read and Grep to examine existing test files in the project to understand:
- Test file naming conventions
- Test framework and assertion patterns
- Project-specific test organization
- Test data setup patterns
-
Design Test Cases: Create comprehensive test coverage including:
- Happy path scenarios with expected inputs
- Edge cases (null, empty, boundary values)
- Error conditions and invalid inputs
- All logical branches and conditions
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.
- 11d ago First seen · 104 lines · 39 tokens per session scan A 16bf3724d142
unit-test-engineer is an agent published in the GitHub repository appboypov/pew-pew-plaza-packs (85 stars, last pushed 8mo ago), licensed MIT. It adds 39 tokens to every session and 991 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-30.
Other agents, from other repositories
qa-automation-engineer
QA automation engineer for unit, integration, API, UI, regression, fixtures, and automation maintainability.
test-writer
Generates tests for code. Use when writing unit tests, integration tests, or component tests with Vitest and React Testing Library.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.