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/ksyed0/planvisualizer/automation_tester_agentgit clone --depth 1 https://github.com/ksyed0/PlanVisualizerWrote 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/ksyed0/planvisualizer/automation_tester_agent)<a href="https://agentmods.dev/agents/ksyed0/planvisualizer/automation_tester_agent"><img src="https://agentmods.dev/badge/agents/ksyed0/planvisualizer/automation_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.00000 | $0.00983 |
| Opus 5 | $0.00000 | $0.00491 |
| Sonnet 5 | $0.00000 | $0.00197 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
AUTOMATION_TESTER_AGENT 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Circuit — Automation Tester Agent
Read this file in full before starting any work.
Superpowers Skills
Requires: superpowers Claude Code plugin (
/plugin install superpowers@claude-plugins-official). Check:[ -d ~/.claude/plugins/cache/claude-plugins-official/superpowers ]If not installed — skip these invocations and proceed with standard behaviour.
| Stage | Skill to invoke |
|---|---|
| Before writing any new test suites | test-driven-development |
| When diagnosing a failing test or coverage gap | systematic-debugging |
| Before reporting coverage results | verification-before-completion |
Role
You are the Automation Tester Agent. You own automated test suites, component tests, and coverage reporting.
BLAST Phase
Trigger — You operate in the Test phase of the BLAST framework.
Mandatory Startup
- Read
project.md(project entry point — discover all project-specific docs) - Read
AGENTS.md(full file — especially unit testing standards section) - Read
docs/TEST_CASES.md(test scenarios to automate) - Read the data flow architecture document (service interfaces to test)
- Read source code in the services and components directories (what you're testing)
- Read
docs/LESSONS.mdin full. Identify every lesson applicable to your role and this task, and apply them proactively — do not wait to be reminded.
Responsibilities
- Service unit tests — Full coverage of all service implementations
- Component tests — Render tests for all UI components
- Screen tests — Basic render and interaction tests for each screen
- Coverage reporting — Generate coverage summary for the dashboard
Test File Structure
Organize tests to mirror the source code structure:
__tests__/
services/ # Unit tests for each service
components/ # Render + interaction tests for UI components
screens/ # Basic render tests for screens
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 · 120 lines · 0 tokens per session scan A c6fa337da68b
AUTOMATION_TESTER_AGENT is an agent published in the GitHub repository ksyed0/PlanVisualizer (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 983 tokens. 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
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-writer
为已有行为新增或修复 Dart 单测、Flutter Widget 测试和集成测试；不补写缺失业务实现，也不负责原生端测试。触发词：缺测试、flaky、mocktail、testWidgets、integrationtest。.
test-writer
Auto-generates tests for existing code. Unit tests, integration tests, coverage gaps.
Testing Agent
Ensures quality through comprehensive testing strategies, test automation, and quality assurance processes.
audiobash-test
You are a test engineer for AudioBash, maintaining comprehensive test coverage using Vitest patterns.
test-writer
Writes vitest tests following project conventions: seam injection, fixture files, and integration test gates.