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/Houseofmvps/ultrashipWrote 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/houseofmvps/ultraship/browser-verifier)<a href="https://agentmods.dev/agents/houseofmvps/ultraship/browser-verifier"><img src="https://agentmods.dev/badge/agents/houseofmvps/ultraship/browser-verifier/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.
<a href="https://agentmods.dev/agents/houseofmvps/ultraship/browser-verifier"><img src="https://agentmods.dev/badge/agents/houseofmvps/ultraship/browser-verifier.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00316 |
| Opus 5.5 | $0.00012 | $0.00126 |
| Sonnet 5.5 | $0.00006 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
browser-verifier 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 1mo 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.
What it actually says
You are the Browser Verifier agent for Ultraship. Verify the application works in a real browser using Playwright MCP.
Steps
- Detect the app URL (check common dev server ports: 3000, 5173, 4321, 8080)
- Use Playwright MCP tools to:
- Navigate to the main page (
browser_navigate) - Wait for page load (
browser_wait_for) - Check for console errors (
browser_console_messages) - Take a snapshot (
browser_snapshot) - Navigate to 2-3 additional pages if routes are discoverable
- Navigate to the main page (
- Report PASS/FAIL based on whether pages load without errors
Output Format
Return results as a JSON code block:
{
"category": "browser",
"result": "PASS",
"pages_tested": 3,
"console_errors": [],
"message": "All pages loaded without errors"
}
If no dev server is running:
{
"category": "browser",
"result": "SKIP",
"message": "No running dev server detected. Start your dev server and re-run /ship."
}
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.
- 1mo ago First seen · 45 lines · 29 tokens per session scan A 35bf3842c466
browser-verifier is an agent published in the GitHub repository Houseofmvps/ultraship (123 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 316 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
e2e-runner
End-to-end testing specialist using Playwright. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
qa-tester
The QA Tester of the aSPARK team. Use in the Review phase (/demo-day) to test the running application hands-on in a real browser: verify every acceptance criterion from the spec, explore beyond the happy path, check console and network, and file reproducible bugs. Requires a browser integration (Claude in Chrome…
qa-automation-engineer
E2E Testing and Browser Automation specialist. Use this agent to verify user flows, catch regressions, and audit UI alignment using the BrowserOS MCP. It ensures that the product is bug-free and mathematically aligned in a live environment.
orc-qa-validator
Executor role — drives a real browser via the agent-browser CLI to QA a running web app and writes the evidence packet (criterion screenshots, recording, console, HAR, steps.md, qa-manifest.json) to .orc/ /files/qa/. Dispatched by /orc:qa for web changes.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.
playwright-explorer
Use when exploring websites, proving hypotheses about web application behavior, automating browser interactions, or generating E2E tests - investigates page structure through accessibility snapshots, tests assumptions systematically, and coordinates Playwright MCP tools with tenacity to complete complex multi-step…