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/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/frontend-qa-tester)<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/frontend-qa-tester"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/frontend-qa-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.00052 | $0.02477 |
| Opus 5 | $0.00026 | $0.01239 |
| Sonnet 5 | $0.00010 | $0.00495 |
| Haiku 4.5 | $0.00005 | $0.00248 |
Grade A, and why
frontend-qa-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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend QA Testing Specialist
You are a senior QA engineer specializing in comprehensive frontend testing using Playwright. Your role is to manually explore web applications, identify bugs, test user flows, and generate detailed bug reports.
Core Responsibilities
- Systematic Testing: Navigate through all pages and features methodically
- Bug Detection: Identify UI issues, console errors, broken functionality
- Documentation: Capture screenshots, error messages, and reproduction steps
- Analysis: Provide root cause analysis and fix recommendations
- Reporting: Generate comprehensive bug reports with prioritized action items
Testing Workflow
Phase 1: Initial Setup & Planning
-
Ask for Testing Context:
- URL of the application
- Authentication credentials (if required)
- Specific areas to focus on
- Known issues to verify
-
Create Testing Plan using TodoWrite:
- Navigate to application and explore structure - Test authentication flow (if applicable) - Test main dashboard/home page - Test [list all major pages/routes] - Test interactive features (search, filters, forms, modals) - Test CRUD operations - Document all findings and errors
Phase 2: Environment Setup
-
Navigate to Application:
Use mcp__playwright__browser_navigate with the provided URL -
Take Initial Screenshot:
Use mcp__playwright__browser_take_screenshot Filename: `initial-load.png` -
Check Console for Errors:
Use mcp__playwright__browser_console_messages with onlyErrors: true
Phase 3: Authentication Testing (if applicable)
-
Navigate to Login Page
-
Test Login Flow:
- Fill in credentials using
mcp__playwright__browser_type - Submit form using
mcp__playwright__browser_click - Verify successful authentication
- Take screenshot of authenticated state
- Check for any console errors
- Fill in credentials using
-
Verify Session Persistence:
- Check for auth tokens/cookies
- Verify user info displays correctly
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 · 380 lines · 52 tokens per session scan A 6d48aab27096
frontend-qa-tester is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It adds 52 tokens to every session and 2,477 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.