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 skills/storybookjs/mcp/codex-browsernpx skills add storybookjs/mcp --skill codex-browsergit clone --depth 1 https://github.com/storybookjs/mcpWrote 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/storybookjs/mcp/codex-browser)<a href="https://agentmods.dev/skills/storybookjs/mcp/codex-browser"><img src="https://agentmods.dev/badge/skills/storybookjs/mcp/codex-browser.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.00067 | $0.00692 |
| Opus 5 | $0.00034 | $0.00346 |
| Sonnet 5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
control-in-app-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 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser
Use this skill for browser automation tasks such as inspecting pages, navigating, testing local apps, clicking, typing, taking screenshots, and reading visible page state.
If this skill is listed as available in the session, treat that as mandatory reading before browser work. Open and follow this skill before saying that Browser is unavailable and before falling back to standalone Playwright or other browser-control mechanisms.
Bootstrap
The browser-client module is the core entry point for browser use, and is available at .agent-eval/mcp/codex-browser-client-mock.mjs relative to the workspace root. ALWAYS import it using an absolute path composed from nodeRepl.cwd. IMPORTANT: If this path cannot be found, stop and report that the workspace is missing .agent-eval/mcp/codex-browser-client-mock.mjs.
Run browser setup code through the Node REPL js tool. In this environment the callable tool id typically appears as mcp__node_repl__js. You need the js execution tool: js_reset only clears state, and js_add_node_module_dir only changes package resolution.
Initialize the runtime once per fresh Node session, select the in-app browser, and immediately read its complete documentation:
if (globalThis.agent?.browsers == null) {
const { setupBrowserRuntime } = await import(
nodeRepl.cwd + '/.agent-eval/mcp/codex-browser-client-mock.mjs'
);
await setupBrowserRuntime({ globals: globalThis });
}
globalThis.browser = await agent.browsers.get('iab');
nodeRepl.write(await browser.documentation());
If setup succeeds but browser discovery or selection fails, read await agent.documentation.get("bootstrap-troubleshooting") before resetting the JavaScript session.
Use the browser bound to browser for tasks in this skill. The ability to interact directly with the browser is exposed through the agent.browsers.* API. Before trying to interact with it, you MUST emit and read the complete documentation returned by await browser.documentation() in one go, using the exact direct call nodeRepl.write(await browser.documentation()); shown above.
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.
- today First seen · 47 lines · 67 tokens per session scan A b04940c1c328
control-in-app-browser is a skill published in the GitHub repository storybookjs/mcp (270 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 692 once invoked, about $0.0003 per session on Opus 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-09-03.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
web-browser
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.
traceway-setup
Analyze and instrument repositories for Traceway observability. Use when the user wants to plan, add, migrate, or verify Traceway or OpenTelemetry monitoring for backend, browser, full-stack, mobile or iOS, or AI-agent software, including project topology and user-approved setup-plan creation. Backends use OTLP/HTTP…