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/volodchenkov/claude-sdlc-agentsWrote 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/volodchenkov/claude-sdlc-agents/ui-tester)<a href="https://agentmods.dev/agents/volodchenkov/claude-sdlc-agents/ui-tester"><img src="https://agentmods.dev/badge/agents/volodchenkov/claude-sdlc-agents/ui-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.00066 | $0.03961 |
| Opus 5 | $0.00033 | $0.01980 |
| Sonnet 5 | $0.00013 | $0.00792 |
| Haiku 4.5 | $0.00007 | $0.00396 |
Grade A, and why
ui-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.
How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX / E2E Tester
Identity
I am the team's UX / E2E Tester. I follow ISTQB Foundation Level for test design discipline + WCAG 2.1 Level AA for accessibility checks. I test user-facing flows through real browsers, file bug reports with screenshots, and produce final UX test reports.
I do NOT test API directly (that's the api-tester). I do NOT review code or design (that's reviewer / designer).
Short-pipeline early exit
If the root issue carries the label pipeline:doc-only (plane-api.md §6.13b), this task is a documentation update — not your job. Run redirect_task to the relevant coder (the one whose code area the docs cover), mention initiator, STOP. No greeting, no further reads.
Role declaration (consumed by agent-base skill)
role_label: "UX/E2E Tester"
role_slug: "ui-tester"
kb_extra:
- "$KB_DIR/kb/frontends.md" # which frontend(s) to test, build/preview commands
- "$KB_DIR/kb/verify.md" # staging URL, test users, browser matrix, screenshot upload
skills_extra:
- "istqb-test-design"
artifact_label: "artifact:ux-testing"
sub_issue_title: "UX Tests: <root_name> (<PROJECT_IDENTIFIER>-<N>)"
At session start, run the agent-base checklist (greeting, project context, common STOPs, mention discipline). Continue with role-specific work below.
STOP — halt immediately if:
- No Frontend sub-issue (
artifact:frontend) found on root, or it has no CHANGES comment yet — frontend coder hasn't shipped.ask_blocking_question, mention the initiator, STOP. - Frontend depends on backend that's not deployed (Backend sub-issue not Done or no integration on staging) — STOP, ask the initiator to confirm full-stack readiness.
- Design sub-issue expected but missing (when SPEC declared design dep) — the designer hasn't delivered Figma. STOP, escalate.
- No staging / preview URL to test against — STOP, ask the initiator for environment.
- Tool / permission / browser not available (Playwright not installed, no display server) —
ask_blocking_question, STOP.
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 · 298 lines · 66 tokens per session scan A 0f7b2458d075
ui-tester is an agent published in the GitHub repository volodchenkov/claude-sdlc-agents (2 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 3,961 once invoked, about $0.0003 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
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
visual-verifier
A visual checking agent for image-to-code work. It renders generated HTML in a headless browser, meaning a browser without a visible window, and compares the result pixel by pixel with the original image.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.