swe-web-tester

swe-web-tester is an agent for Claude Code from wahidyankf/ose-public. It costs 47 tokens per session (1,329 once invoked), scanned A, original, MIT.

A web testing agent that uses a real browser to inspect a running website against a specification, approved design, or predefined exploratory checks. It records findings and does not fix the site.

In plain words
What is it for?
It helps check web behaviour, visual design fidelity, accessibility issues, and differences from documented scenarios, with steps for reproducing each finding.
Why use it?
It tests what users actually encounter in the running interface rather than relying only on source code or automated scanners.

Agent for Claude Code

Written for Claude Code: when-to-use in frontmatter. Also seen: installed under .agents/ (shared by several agents).

Good fit It helps check web behaviour, visual design fidelity, accessibility issues, and differences from documented scenarios, with steps for reproducing each finding.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/wahidyankf/ose-public/swe-web-tester
Install

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.

Clone the repo
git clone --depth 1 https://github.com/wahidyankf/ose-public

Made for: Claude Code.

Wrote 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.

agentmods badge for swe-web-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/wahidyankf/ose-public/swe-web-tester/github.svg)](https://agentmods.dev/agents/wahidyankf/ose-public/swe-web-tester)
Your own site
<a href="https://agentmods.dev/agents/wahidyankf/ose-public/swe-web-tester"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/swe-web-tester/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.

agentmods 80×15 button for swe-web-tester

Your own site · 80×15
<a href="https://agentmods.dev/agents/wahidyankf/ose-public/swe-web-tester"><img src="https://agentmods.dev/badge/agents/wahidyankf/ose-public/swe-web-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,329 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01329
Opus 5.5 $0.00019 $0.00532
Sonnet 5.5 $0.00009 $0.00266
Haiku 4.5 $0.00005 $0.00133

Measured today against content hash 837f9ae82058, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

swe-web-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 today.

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.

.agents/agents/swe-web-tester.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SWE Web Tester

Judges what a user meets in a running web interface, through a real browser at the served origin. It never edits source, tests, designs, or specifications; repository-write serves its findings record and captures alone.

Normal Workload

Under the charter its caller names, it drives the interface, compares each observation with a cited scenario, design source, or computation, and rates what differs. Judging each observation against fixed sources takes high-context judgement about what a difference means, so this is plan work.

Charter

The caller names one charter per pass. With none named, it asks rather than guessing.

Charter Judges Inside
spec behaviour, design fidelity, and accessibility no scanner settles, against the specification UI Web Quality Gate, as its judge
design the render against approved designs, runtime tokens, primitives, and cited design practice UX Review Fix Planning, third pass
exploratory behaviour against specifications, contracts, and designs, within charters frozen before the pass Exploratory and Usability Review, first

Read the full file on GitHub · 93 lines

Changes

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.

  1. today Changed · +1 lines 837f9ae82058
  2. 2d ago First seen · 92 lines · 47 tokens per session scan A c89013e208c2

Subscribe to this mod's changes

swe-web-tester is an agent published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,329 once invoked, about $0.0002 per session on Opus 5.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-10-14.

Related

Other agents, from other repositories

playwright-automation-engineer-ts-detailed

Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.

jaktestowac/awesome-copilot-for-testers · 54 tokens

webkit-ui-verifier

Runs the visual and behavioral QA pass on a @aziontech/webkit app — builds and serves it, drives real routes with headless Chromium, and reports only what it observed across themes, console, a11y, states, and interaction.

aziontech/webkit · 55 tokens

integ-test-runner

Runs integ-test-playbook.md per cycle to close or assess this cycle's implemented features and verify-set beads (any issuetype, all children closed) against real evidence; closes passing ones, files [integ] bugs for failures.

Apra-Labs/apra-fleet · 53 tokens

hcc-frontend-iqe-to-playwright-converter

Use this agent to convert IQE/Selenium tests to Playwright TypeScript. This agent implements proper Red Hat SSO authentication (global or isolated), converts fixtures and page objects, modernizes selectors and wait patterns, uses symbolic timeout constants, handles parametrized tests, and organizes converted files by…

RedHatInsights/platform-frontend-ai-toolkit · 215 tokens

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.).

DevZonayed/Mochi · 60 tokens

visual-diagram-verifier

Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…

sembraniteam/claude-plugins · 112 tokens