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/CreatmanCEO/notebooklm-claude-workflowsWrote 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/creatmanceo/notebooklm-claude-workflows/telegram-to-notebook)<a href="https://agentmods.dev/commands/creatmanceo/notebooklm-claude-workflows/telegram-to-notebook"><img src="https://agentmods.dev/badge/commands/creatmanceo/notebooklm-claude-workflows/telegram-to-notebook.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.00000 | $0.00675 |
| Opus 5 | $0.00000 | $0.00338 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
telegram-to-notebook 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/telegram-to-notebook — Импорт Telegram-чата в NotebookLM
Загружает экспорт Telegram-чата в NotebookLM. Поддерживает форум-чаты с темами (topics). Фильтрует стикеры, GIF, видео. Сохраняет текст, код, PDF, документы.
Параметр
$ARGUMENTS — путь к JSON-файлу экспорта Telegram ИЛИ название чата
Предварительный шаг (пользователь делает сам)
- В Telegram Desktop: чат → три точки → Export chat history
- Формат: JSON (Machine-readable)
- Медиа — можно не снимать, скрипт сам отфильтрует
Действия
Шаг 1: Определи тип чата
- Запусти скрипт с
--list-topicsчтобы определить структуру:python ~/notebooklm-claude-toolkit/scripts/telegram-chunker.py "$ARGUMENTS" --list-topics - Если чат содержит топики (форум) — предложи варианты:
- По темам (
--per-topic): отдельный файл на каждую тему — лучше для целевого анализа - Выборочно (
--per-topic --topics "Docker,FAQ"): только конкретные темы - Всё вместе (без флагов): один файл с заголовками тем — лучше для общего обзора
- По темам (
Шаг 2: Конвертация
- Запусти скрипт с выбранным режимом:
# Все темы по отдельности python ~/notebooklm-claude-toolkit/scripts/telegram-chunker.py "$ARGUMENTS" --per-topic # Конкретные темы python ~/notebooklm-claude-toolkit/scripts/telegram-chunker.py "$ARGUMENTS" --per-topic --topics "Docker,Feature requests" # Всё вместе (обычный чат или общий обзор) python ~/notebooklm-claude-toolkit/scripts/telegram-chunker.py "$ARGUMENTS" - Скрипт выведет: количество сообщений, слов, пропущенных (стикеры/GIF/видео), созданных файлов
Шаг 3: Загрузка в NotebookLM
- Создай ноутбук "Telegram: [название чата]" через
notebook_create - Для каждого файла из output-dir:
- Прочитай содержимое файла
- Добавь через
source_add:source_type: "text"text: содержимое файлаtitle: имя файла (например "Telemt_Docker")wait: true
- Показывай прогресс: "Загружено 3/13 файлов..."
- Покажи итог: название ноутбука, ID, количество источников, слов
- Предложи задать вопрос через
notebook_query
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 · 58 lines · 0 tokens per session scan A 8d191792b176
telegram-to-notebook is a command published in the GitHub repository CreatmanCEO/notebooklm-claude-workflows (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 675 tokens. 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
create-pdf
Generate a professional PDF document using Python and reportlab.
ars-format-convert
ARS academic-paper format-convert mode — convert to LaTeX / DOCX / PDF / Markdown.
council-extract
Extract a completed Perplexity Model Council response from the current browser tab, converting it to structured markdown with model attribution, and save to disk.
latex-polish
Inspect a cleanly compiling LaTeX document for source pathologies and rendered visual defects by linting and viewing selected PDF pages. Use when compilation succeeds but title pages, floats, tables, figures, or layout still need publication-quality review. Not for basic compilation health; use $latex-health-check.
latex
Compile one specified LaTeX document, resolve build errors, audit citations, and report build quality. Use when a .tex source must be built or a concrete compilation failure repaired. Not for corpus-wide build checks, visual polish after a clean build, or creating a project; use $latex-health-check, $latex-polish, or…
bib-filter
Filter a LaTeX project's bibliography to the entries actually cited, with Overleaf-source resolution, temporary staging, validation, approval-gated canonical replacement, and compilation. Use before submission or after large revisions.