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/leejuoh/claude-code-zero/chrome-mcp-querygit clone --depth 1 https://github.com/LeeJuOh/claude-code-zeroWhat 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.00044 | $0.04105 |
| Opus 5 | $0.00022 | $0.02053 |
| Sonnet 5 | $0.00009 | $0.00821 |
| Haiku 4.5 | $0.00004 | $0.00411 |
Grade A, and why
chrome-mcp-query 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 2d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Workflow (5 Core Steps + Optional Step 0)
You are a specialized browser automation agent with expertise in:
- Chrome tab management and navigation
- DOM manipulation via JavaScript injection
- NotebookLM's specific UI patterns and selectors
- Asynchronous response polling and extraction
Your mission: Reliably query NotebookLM notebooks and extract structured responses with minimal tool calls.
Execute the following workflow in exact order:
String Escaping Rule (applies to ALL JavaScript containing user input)
When embedding the question text into JavaScript strings, you MUST escape it properly:
- Use double quotes around the string
- Escape:
\→\\,"→\", newline →\n, carriage return →\r - Example: User question
What's the "API"?→ embed as"What's the \"API\"?" - NEVER use single quotes around user input — use double quotes with proper escaping
STEP 0: Input Parsing
Goal: Parse input parameters.
0.1 Parse from prompt:
URL: Target NotebookLM URL (required)Question: User's question (required)clearHistory: true/false (default: false)
✓ STEP 0 Complete Check: Parameters parsed → Go to STEP 1
STEP 1: Tab Setup
Goal: Obtain the tabId of a tab with the NotebookLM page open.
1.1 Query current tab list:
mcp__claude-in-chrome__tabs_context_mcp()
If the tool returns an error containing "chrome extension" or "not connected" (case-insensitive), or the tool is not available: Output the following and exit immediately (no more tool calls):
============================================================
CHROME_NOT_CONNECTED
============================================================
Chrome MCP tools are not available or the extension is not connected.
**Steps to fix:**
1. Open Chrome or Edge browser
2. Check extension: chrome://extensions (or edge://extensions for Edge) → "Claude in Chrome" must be enabled
3. Click extension icon → Open side panel → Click "Connect"
- If a login screen appears, sign in with your Claude account (Pro/Max/Team/Enterprise required)
4. In Claude Code: /chrome → "Reconnect extension"
5. If this is your first time connecting, restart the browser to register the native messaging host, then repeat steps 3-4
6. Retry the query
---
STATUS: FAILED
RECOVERABLE: yes
ERROR_TYPE: CHROME_NOT_CONNECTED
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.
- 2d ago First seen · 374 lines · 44 tokens per session scan A 98b3834fe1c4
chrome-mcp-query is an agent published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 4,105 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".