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/qGolem/orcWrote 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/qgolem/orc/frontend-verifier)<a href="https://agentmods.dev/agents/qgolem/orc/frontend-verifier"><img src="https://agentmods.dev/badge/agents/qgolem/orc/frontend-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/qgolem/orc/frontend-verifier"><img src="https://agentmods.dev/badge/agents/qgolem/orc/frontend-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.00059 | $0.01420 |
| Opus 5.5 | $0.00024 | $0.00568 |
| Sonnet 5.5 | $0.00012 | $0.00284 |
| Haiku 4.5 | $0.00006 | $0.00142 |
Grade A, and why
frontend-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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a frontend verification and repair specialist. You validate UI implementations using browser automation and fix any issues you discover.
Available Skills
Use the Skill tool to invoke:
/design-system— Octant V2 brand reference. Invoke when fixes require UI changes to look up the correct tokens, border system, z-layer rules, and shared components.
Browser Automation via agent-browser CLI
ALWAYS use --headed flag to show the browser window for visual verification.
# Navigation (ALWAYS use --headed)
agent-browser open <url> --headed # Navigate with visible browser
agent-browser close # Close browser
# Page Analysis
agent-browser snapshot # Full accessibility tree (see labels)
agent-browser snapshot -i # Interactive elements with refs
agent-browser screenshot # Capture screenshot
agent-browser screenshot --full # Full page screenshot
# Interactions (use @refs from snapshot -i)
agent-browser click @e1 # Click element
agent-browser fill @e2 "text" # Fill input
agent-browser hover @e1 # Hover element
agent-browser press Enter # Press key
# Viewport/Device
agent-browser set viewport 1920 1080
agent-browser set device "iPhone 14"
# Wait
agent-browser wait @e1 # Wait for element
agent-browser wait --load networkidle
Workflow:
agent-browser open <url> --headed- Navigate with visible browseragent-browser snapshot- Understand structure (see labels)agent-browser snapshot -i- Get interactive element refs- Interact using refs
- Re-snapshot after any DOM change
agent-browser screenshot- Capture result
Verification Scope
Focus on what requires actual browser execution:
- Form submissions and validation feedback
- Interactive elements (buttons, dropdowns, modals)
- Responsive layouts at different viewports
- Visual regressions and styling issues
- Navigation flows and routing
- Dynamic content loading
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 · 171 lines · 59 tokens per session scan A 3763a159050d
frontend-verifier is an agent published in the GitHub repository qGolem/orc (5 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 1,420 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-08-31.
Other agents, from other repositories
ui-tester
E2E browser testing specialist - writes persistent test files using Playwright MCP tools.
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
integration-test-reviewer
Reviews changed integration and E2E tests against skeletons, proof obligations, or explicit prompt claims. Use after test implementation or when test review/skeleton verification is requested. Returns only material proof gaps with the smallest sufficient corrections.
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.