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 commands/minihellboy/notebooklm-papers-plugin/export-slidesgit clone --depth 1 https://github.com/minihellboy/notebooklm-papers-pluginWhat 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.00008 | $0.00434 |
| Opus 5 | $0.00004 | $0.00217 |
| Sonnet 5 | $0.00002 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
export-slides 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 yesterday.
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
Export Slides
Export slide decks from one or more NotebookLM notebooks to Google Slides.
Arguments
Parse from: $ARGUMENTS
Options:
--all: Export from all recent paper notebooks--filter "TERM": Export from notebooks matching term--recent N: Export from N most recent notebooks--urls URL1 URL2...: Export from specific notebook URLs
Workflow
For All/Filtered Export
- Navigate to NotebookLM homepage
- Get list of notebooks (apply filters if specified)
- For each notebook: a. Open the notebook b. Check if slide deck exists in Studio panel c. If exists, click the slide deck to open viewer d. Click Download button to export to Google Slides e. Track progress
- Report all exported slides
For Specific URLs
- For each provided URL: a. Navigate to the notebook b. Find and click the slide deck c. Click Download to export
- Report completion
Example Usage
# Export all paper notebooks
/notebooklm-papers:export-slides --all
# Export recent 5 notebooks
/notebooklm-papers:export-slides --recent 5
# Export matching filter
/notebooklm-papers:export-slides --filter "Paper"
# Export specific notebooks
/notebooklm-papers:export-slides --urls https://notebooklm.google.com/notebook/abc123 https://notebooklm.google.com/notebook/def456
Output
Reports:
- Number of notebooks processed
- Number of slide decks exported
- Any notebooks without slide decks
- Google Slides links (opened in new tabs)
Notes
- Slide decks export to Google Slides in the user's Google Drive
- User can manually download as PDF/PPTX from Google Slides
- Notebooks without generated slide decks are skipped
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.
- yesterday First seen · 69 lines · 8 tokens per session scan A 08445cde2953
export-slides is a command published in the GitHub repository minihellboy/notebooklm-papers-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 434 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.