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/robinsadeghpour/content-workflow/notebooklm-setupnpx skills add robinsadeghpour/content-workflow --skill notebooklm-setupgit clone --depth 1 https://github.com/robinsadeghpour/content-workflowWrote 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/robinsadeghpour/content-workflow/notebooklm-setup)<a href="https://agentmods.dev/skills/robinsadeghpour/content-workflow/notebooklm-setup"><img src="https://agentmods.dev/badge/skills/robinsadeghpour/content-workflow/notebooklm-setup.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.00087 | $0.00789 |
| Opus 5 | $0.00044 | $0.00394 |
| Sonnet 5 | $0.00017 | $0.00158 |
| Haiku 4.5 | $0.00009 | $0.00079 |
Grade A, and why
notebooklm-setup 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NotebookLM Setup
Install notebooklm-py — an unofficial Python CLI for Google NotebookLM — and register its Claude Code skill.
What gets installed
| Component | Purpose |
|---|---|
| pipx | Isolated Python app installer (if not already present) |
| notebooklm-py | CLI for NotebookLM (notebooklm command) |
| Playwright chromium | Headless browser used for Google OAuth login |
| Claude Code skill | ~/.claude/skills/notebooklm/SKILL.md — enables /notebooklm and natural language automation |
Setup steps
Run each step in order. Check the output before proceeding — if a step fails, troubleshoot before continuing.
1. Install pipx
pipx manages Python CLI tools in isolated virtual environments, avoiding conflicts with system Python.
which pipx || brew install pipx
If Homebrew isn't available, fall back to python3 -m pip install --user pipx.
2. Install notebooklm-py
The [browser] extra pulls in Playwright, which is needed for the login flow.
pipx install "notebooklm-py[browser]"
If already installed, upgrade instead:
pipx upgrade notebooklm-py
Verify the CLI is available:
notebooklm --version
3. Install Playwright chromium
Playwright needs its own bundled Chromium binary. Install it inside the notebooklm-py virtualenv:
~/.local/pipx/venvs/notebooklm-py/bin/playwright install chromium
On Linux, you may also need system dependencies: playwright install-deps chromium.
4. Install the Claude Code skill
This copies the skill file into ~/.claude/skills/notebooklm/:
notebooklm skill install
5. Authenticate with Google
This step requires user interaction — a browser window opens for Google OAuth. Tell the user to run this themselves:
notebooklm login
After login, verify auth works:
notebooklm auth check
Troubleshooting
| Problem | Fix |
|---|---|
externally-managed-environment error from pip |
Use pipx instead of pip |
playwright: command not found |
Use the full venv path: ~/.local/pipx/venvs/notebooklm-py/bin/playwright |
| Auth errors after setup | Re-run notebooklm login |
| Skill not showing in Claude Code | Re-run notebooklm skill install, then restart Claude Code session |
notebooklm: command not found after pipx install |
Run pipx ensurepath and restart your shell |
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 · 102 lines · 87 tokens per session scan A 4505dcf627f2
notebooklm-setup is a skill published in the GitHub repository robinsadeghpour/content-workflow (55 stars, last pushed 3mo ago), licensed MIT. It adds 87 tokens to every session and 789 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…