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/datacore-one/datacore/create-podcastgit clone --depth 1 https://github.com/datacore-one/datacoreWrote 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/datacore-one/datacore/create-podcast)<a href="https://agentmods.dev/commands/datacore-one/datacore/create-podcast"><img src="https://agentmods.dev/badge/commands/datacore-one/datacore/create-podcast.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.00008 | $0.01715 |
| Opus 5 | $0.00004 | $0.00857 |
| Sonnet 5 | $0.00002 | $0.00343 |
| Haiku 4.5 | $0.00001 | $0.00171 |
Grade A, and why
create-podcast 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 today.
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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Podcast Command
Command Context
When to Reference Research Module
Always reference when:
- User wants custom podcast on specific topic outside daily processing
- Need to compile research on focused subject (competitive analysis, market trends)
- Want to create learning material from curated sources
- Testing podcast generation before nightshift processing
- Need podcast from specific research_learning.org section
Key decisions this command informs:
- Whether to provide URLs directly or pull from research_learning.org
- Optimal source count for topic depth (5-10 recommended)
- Custom instructions for podcast style (competitive, educational, market research)
- When to create multiple focused podcasts vs one broad podcast
Quick Reference
| Question | Answer |
|---|---|
| What inputs does it accept? | Direct URLs, research_learning.org section, or interactive prompts |
| What's the optimal source count? | 5-10 sources for depth (min 3, max 12) |
| How long does generation take? | 5-10 minutes typically, timeout at 30 minutes |
| Where are podcasts saved? | 0-personal/content/podcasts/ or team space |
Agents This Command Invokes
| Agent | Purpose |
|---|---|
| podcast-creator | Manages full podcast lifecycle: notebook creation, source addition, audio generation, download |
Integration Points
- podcast-creator agent - Invoked with user-provided sources and topic
- research_learning.org - Optional source for pulling URLs by section
- nlm CLI - External NotebookLM integration tool
- Podcast output directory - Files saved to designated location
- User confirmation - Interactive prompts for source selection and settings
Create an ad-hoc NotebookLM podcast from provided URLs or a topic.
Usage
/create-podcast [options]
Input Options
Option 1: Direct URLs
User provides specific URLs:
/create-podcast
URLs:
- https://article1.com
- https://article2.com
- https://article3.com
Topic: "Market Analysis Q4"
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.
- today First seen · 308 lines · 8 tokens per session scan A 4ec92a746cc0
create-podcast is a command published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 1,715 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-09-03.
Other commands, from other repositories
prd-review
Review the active PRD with Codex and stream normalized findings to JSONL.
prd-archive
Archive the active PRD (blocked until every accepted finding has a receipt).
prd-map
Build a codebase map so PRDs are written with repo context, not blind.
prd-split
Split the approved PRD into one issue spec per manifest entry.
rca-check
Lint an RCA or premortem document against the canonical template.
prd-os-init
Initialize prd-os in this repo (writes .prd-os/config.json).