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 instructions/faxtom/notebooklm-mcp/claude-mdgit clone --depth 1 https://github.com/Faxtom/notebooklm-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/instructions/faxtom/notebooklm-mcp/claude-md)<a href="https://agentmods.dev/instructions/faxtom/notebooklm-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/faxtom/notebooklm-mcp/claude-md.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.01272 | $0.01272 |
| Opus 5 | $0.00636 | $0.00636 |
| Sonnet 5 | $0.00254 | $0.00254 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
notebooklm-mcp CLAUDE.md 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 4d 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.
This is a copy
100% identical to notebooklm-mcp-2026 CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Project Is
An MCP (Model Context Protocol) server that lets AI assistants query Google NotebookLM notebooks. Authenticates via Chrome CDP cookie extraction, communicates with Google's internal batchexecute RPC API, and exposes 9 tools over stdio JSON-RPC. Built with FastMCP, httpx, and Rich.
Commands
# Install
pip install -e ".[dev]"
# Lint
ruff check src/ tests/
# Test
pytest -v --tb=short
pytest -k "not chrome" # skip Chrome-dependent tests
pytest tests/test_protocol.py -v # run one test file
pytest -k "test_build_rpc_body" # run one test by name
# Run
notebooklm-mcp-2026 serve # start MCP server (stdio)
notebooklm-mcp-2026 login # interactive Chrome login
notebooklm-mcp-2026 logout # remove stored credentials
notebooklm-mcp-2026 setup # interactive setup wizard
notebooklm-mcp-2026 doctor # diagnose common issues
notebooklm-mcp-2026 status # show auth + config status
notebooklm-mcp-2026 version # print version
notebooklm-mcp-2026 help # show help message
All CLI subcommands support --debug for verbose logging. The setup command also supports --dry-run.
Architecture
5-layer stack, each layer only calls the one below it:
MCP Clients (Claude Desktop, etc.)
└─ server.py — FastMCP instance + global client singleton (get_client())
└─ tools/ — 9 tool functions: validate input → call client → return dict
└─ client.py — NotebookLMClient: HTTP requests, auth retry, backoff
└─ protocol.py — Pure functions: build RPC bodies, parse responses (zero I/O)
auth.py — Chrome CDP cookie extraction + secure disk storage
Data flow: MCP JSON-RPC → server.py dispatches → tool function → get_client() returns singleton → NotebookLMClient method → protocol.build_*() encodes request → httpx POST → protocol.parse_*() decodes → dict response back up the stack.
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.
- 4d ago First seen · 108 lines · 1,272 tokens per session scan A e8fe4b01b653
notebooklm-mcp CLAUDE.md is an instructions file published in the GitHub repository Faxtom/notebooklm-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,272 tokens to every session, about $0.0064 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to notebooklm-mcp-2026 CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.