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.
git clone --depth 1 https://github.com/gfsaaser24/notebooklm-coworkWrote 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/commands/gfsaaser24/notebooklm-cowork/notebook-create)<a href="https://agentmods.dev/commands/gfsaaser24/notebooklm-cowork/notebook-create"><img src="https://agentmods.dev/badge/commands/gfsaaser24/notebooklm-cowork/notebook-create.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.1 | $0.00009 | $0.00204 |
| Opus 5 | $0.00005 | $0.00102 |
| Sonnet 5 | $0.00002 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
notebook-create 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 8d 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.
What it actually says
The user wants to create a new NotebookLM notebook. Title hint: $ARGUMENTS
Steps:
- Create the notebook with
notebook_create(title="$ARGUMENTS"). - Ask the user what sources to add. Supported types:
- URLs (articles, web pages)
- Plain text or pasted content
- Google Drive documents (by document ID)
- Local files (PDF, DOCX, TXT, etc.)
- For each source, call
source_add()with the appropriatesource_type.- For URLs, set
wait=Trueso processing completes before the next step.
- For URLs, set
- After all sources are added, call
notebook_describe(notebook_id)to confirm the notebook was populated correctly. - Tell the user their notebook is ready and suggest next steps: query it, create studio artifacts, or start research.
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.
- 8d ago First seen · 22 lines · 9 tokens per session scan A ce46d6a1e7be
notebook-create is a command published in the GitHub repository gfsaaser24/notebooklm-cowork (10 stars, last pushed 2mo ago), licensed MIT. It adds 9 tokens to every session and 204 once invoked, about $0.0000 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 commands, from other repositories
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
start-0-8
A Japanese-language command that displays the current project setup progress.