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 skills add DevZonayed/Mochi --skill browsergit clone --depth 1 https://github.com/DevZonayed/MochiWrote 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/skills/devzonayed/mochi/browser)<a href="https://agentmods.dev/skills/devzonayed/mochi/browser"><img src="https://agentmods.dev/badge/skills/devzonayed/mochi/browser/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/skills/devzonayed/mochi/browser"><img src="https://agentmods.dev/badge/skills/devzonayed/mochi/browser.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.00050 | $0.01534 |
| Opus 5.5 | $0.00020 | $0.00614 |
| Sonnet 5.5 | $0.00010 | $0.00307 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
browser 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser
Use the Mochi browser MCP tools for browser automation and QA.
Finding the tools
When installed as a Claude Code plugin, the MCP server registers as
plugin:mochi:browser. The actual tool names use underscores in the
namespace prefix: mcp__plugin_mochi_browser__browser_session_start,
mcp__plugin_mochi_browser__browser_screenshot, etc.
If you don't see them in your current toolset, search via ToolSearch:
select:mcp__plugin_mochi_browser__browser_session_health (and similar).
Schemas are loaded on demand.
When written without prefix below (e.g. "call browser_navigate"), the
full callable name is mcp__plugin_mochi_browser__browser_navigate.
Conflict-with-extension note (HISTORICAL — no longer applies)
Earlier versions of this plugin had a duplicate MCP-server registration
that competed with the Mochi Chrome extension over chrome.debugger
attachments. The unified plugin (v0.2+) eliminates this — there is no
extension-vs-MCP conflict anymore. If your memory has an old "browser MCP
conflicts with the Mochi extension" note from a prior session, it's stale.
Gotchas (read before trusting results)
Hard-won quirks that produce false "all clear" results. The full note with fixes
lives in references/gotchas.md — read it before
reporting a pass.
- Console buffer is stale. Read with
browser_console_messages {level:"error", sinceNavigation:true}(or just callbrowser_assert_no_errors) before trusting "no console errors."level:"error"includes uncaught exceptions. - Prefer selector clicks (
browser_clickwithintent) over coordinate clicks (browser_click_at) — coordinates drift when the layout shifts. - Viewport:
browser_emulate_viewportchangeswindow.innerWidth/matchMedia(real JS layout — use it for media-query/responsive tests);browser_window_resizeonly moves the OS window and does NOT affect JS layout. Don't conflate them. - Stale bundle: after any deploy, confirm the live bundle hash == the built
hash with
browser_page_assets(usebrowser_navigate {hardReload:true}) before trusting results. - Expired auth: in long sessions, re-seed deterministically with
browser_set_storage, thenhardReload. - Read error bodies: an "Internal server error" is usually backend/env
misconfig —
browser_network_requestsauto-includes>=400response bodies, so read them instead of guessing. - Render != Works: a visible/clickable control is not verified. Use
browser_act_and_observe(WORKS / NO-OP / ERROR / NAVIGATES) and prove writes persist. Enumerate every control withbrowser_audit_interactivesbefore claiming "tested everything," and never report pass with untested controls.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 136 lines · 50 tokens per session scan A 629a1546ca35
browser is a skill published in the GitHub repository DevZonayed/Mochi (3 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,534 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 skills, from other repositories
qa-runner
Use when asked to "run QA", "qa check", "test checklist", or execute QA checklists against a running app via browser automation. Requires the browser-bridge MCP server and Chrome extension.
webapp-testing
Write and run comprehensive web app tests — unit, integration, E2E with Playwright/Cypress, and visual regression.
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
cypress-ops
Cypress end-to-end and component testing operations - selector/retry-ability strategy, cy.intercept network stubbing, cy.session auth, component vs e2e, flake diagnosis, CI, Test Replay. Use for: cypress, e2e test, component test, cy.get, cy.intercept, cy.session, data-cy, data-test, retry-ability, flake, flaky test…
playwright-ops
Playwright end-to-end testing operations - selectors, fixtures, network mocking, auth, parallelism, CI, visual regression, flake hunting. Use for: playwright, e2e test, end-to-end testing, browser test, getByRole, page object, storageState, trace viewer, flaky test, test sharding, visual regression, toHaveScreenshot…
webapp-tester
Activates WebAppTester for automated web application testing strategy, test case design, and quality assurance. Use when you need to design a test plan for a web app, write Playwright or Cypress end-to-end tests, create API integration test suites, design accessibility test checklists, or analyze test coverage gaps.