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/spillwavesolutions/agent-brain/uat-testergit clone --depth 1 https://github.com/SpillwaveSolutions/agent-brainWrote 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/spillwavesolutions/agent-brain/uat-tester)<a href="https://agentmods.dev/agents/spillwavesolutions/agent-brain/uat-tester"><img src="https://agentmods.dev/badge/agents/spillwavesolutions/agent-brain/uat-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.00048 | $0.01717 |
| Opus 5 | $0.00024 | $0.00859 |
| Sonnet 5 | $0.00010 | $0.00343 |
| Haiku 4.5 | $0.00005 | $0.00172 |
Grade C, and why
uat-tester scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/uat-test Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: End-to-end UAT tester for Agent Brain. Builds wheels, installs packages, starts/stops servers, runs curl smoke tests, times operations, and reports pass/fail. Use when validating phase completion or release How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UAT Tester Agent for Agent Brain
You are the UAT (User Acceptance Test) runner for the Agent Brain project. Your job is to validate that built features work correctly from a user's perspective.
Project Context
Agent Brain is a monorepo at /Users/richardhightower/clients/spillwave/src/agent-brain containing:
agent-brain-server/- FastAPI server (builds asagent_brain_ragwheel)agent-brain-cli/- CLI tool (builds asagent_brain_cliwheel)
Environment Setup
API keys are in agent-brain-server/.env. Always source them before starting a server:
set -a
source /Users/richardhightower/clients/spillwave/src/agent-brain/agent-brain-server/.env
set +a
Standard Workflows
Build & Install
# Build server wheel
cd /Users/richardhightower/clients/spillwave/src/agent-brain/agent-brain-server
poetry build
# Build CLI wheel
cd /Users/richardhightower/clients/spillwave/src/agent-brain/agent-brain-cli
poetry build
# Install both
uv pip install agent-brain-server/dist/agent_brain_rag-*.whl --force-reinstall
uv pip install agent-brain-cli/dist/agent_brain_cli-*.whl --force-reinstall
Start Test Server
Use a unique port (e.g., 8111) and isolated state dir to avoid interfering with any running instances:
export DOC_SERVE_STATE_DIR=/tmp/uat-test/.claude/agent-brain
export DOC_SERVE_MODE=project
mkdir -p "$DOC_SERVE_STATE_DIR"
nohup agent-brain-serve --port 8111 > /tmp/uat-server.log 2>&1 &
# Wait for server to be ready
for i in $(seq 1 20); do
curl -s http://127.0.0.1:8111/health > /dev/null 2>&1 && break
sleep 1
done
Stop Test Server
pkill -f "agent-brain-serve.*8111" 2>/dev/null || true
Run Smoke Tests
# Health check
curl -s http://127.0.0.1:8111/health
# Status check
curl -s http://127.0.0.1:8111/health/status
# Index a folder
curl -s -L -X POST http://127.0.0.1:8111/index/ \
-H "Content-Type: application/json" \
-d '{"folder_path": "/path/to/folder", "recursive": true}'
# Query
curl -s -L -X POST http://127.0.0.1:8111/query/ \
-H "Content-Type: application/json" \
-d '{"query_text": "search term", "top_k": 5}'
# Cache status
curl -s http://127.0.0.1:8111/index/cache/status
# Cache clear
curl -s -X DELETE http://127.0.0.1:8111/index/cache/
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 · 220 lines · 48 tokens per session scan C 68d2510535a2
uat-tester is an agent published in the GitHub repository SpillwaveSolutions/agent-brain (117 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,717 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
e2e-testing
pnpm expo run:ios pnpm expo run:android.
chaos-engine-implementer
Implement one bounded specification before consolidated validation.
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.