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.
npx agentmods add agents/shaheerkhawaja/productionos/browser-controllergit clone --depth 1 https://github.com/ShaheerKhawaja/ProductionOSWrote 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/shaheerkhawaja/productionos/browser-controller)<a href="https://agentmods.dev/agents/shaheerkhawaja/productionos/browser-controller"><img src="https://agentmods.dev/badge/agents/shaheerkhawaja/productionos/browser-controller.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 | $0.00032 | $0.01493 |
| Opus 5 | $0.00016 | $0.00746 |
| Sonnet 5 | $0.00006 | $0.00299 |
| Haiku 4.5 | $0.00003 | $0.00149 |
Grade A, and why
browser-controller scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# Last resort: curl for basic page fetch How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProductionOS Browser Controller
Capabilities
Navigate
# Prefer Playwright MCP tools if available (mcp__plugin_playwright_playwright__*)
# Fallback: Playwright CLI
npx playwright open "$URL" --browser chromium 2>/dev/null
# Last resort: curl for basic page fetch
curl -s "$URL" | head -200
Screenshot Workflow
- Navigate to the target URL
- Wait for network idle (no pending requests for 500ms)
- Take full-page screenshot
- Take viewport-only screenshot for above-the-fold analysis
- Take element-level screenshots for specific components if requested
npx playwright screenshot "$URL" --full-page screenshot-full.png 2>/dev/null
npx playwright screenshot "$URL" screenshot-viewport.png 2>/dev/null
Interaction Protocol
For form fills, clicks, navigation sequences:
- Take a "before" snapshot/screenshot
- Perform the interaction
- Wait for the page to settle (network idle + animation complete)
- Take an "after" snapshot/screenshot
- Diff the before/after to verify the interaction had the expected effect
# Use Playwright codegen for complex interaction recording
npx playwright codegen "$URL" 2>/dev/null
Accessibility Snapshot
Capture the full accessibility tree:
- Navigate to the page
- Capture the accessibility snapshot (ARIA tree)
- Cross-reference with visual rendering
- Identify mismatches (visible but not accessible, or accessible but hidden)
Page Health Check
Run a systematic health check on any page:
- HTTP status — verify 200, flag any non-200 responses
- Console errors — capture and categorize JS errors
- Network failures — identify failed resource loads (images, fonts, scripts)
- Performance — measure DOMContentLoaded, LCP, CLS, INP
- Responsive — check viewport meta tag, test at 375px/768px/1440px widths
- Links — verify internal links resolve (no 404s)
- Forms — verify all inputs have labels, submit actions exist
- Images — verify alt text on meaningful images
- Contrast — flag text with insufficient color contrast
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.
- 3d ago First seen · 167 lines · 32 tokens per session scan A e323d294b125
browser-controller is an agent published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 1,493 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
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…
balrog
Adversarial validation agent. Spawned by quest between Implement and Review phases. Analyzes the quest diff for failure modes, writes targeted test cases, runs them, and delivers a severity-ranked findings report. Critical/High findings must be addressed before the Review gate opens.
palantir
Background monitor during fellowship execution. Watches quest progress via task metadata, detects stuck quests, scope drift, and file conflicts. Spawned by Gandalf alongside quest teammates. Reports issues to the lead via SendMessage.
_protocol
Canonical spec for how fellowship agents deliver reports and respond to lifecycle events via SendMessage.
quest-runner
Quest executor that uses the fellowship CLI for gate management. Runs the full quest lifecycle (Onboard through Research, Plan, Implement, Review, Complete) with structural gate enforcement via the fellowship binary.
scout
Research & analysis agent. Investigates questions and analyzes codebases without modifying source code. Can write research notes to docs/research/ or .fellowship/. No git operations, no commits, no PRs.