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 agents/datacore-one/datacore/podcast-creatorgit 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/agents/datacore-one/datacore/podcast-creator)<a href="https://agentmods.dev/agents/datacore-one/datacore/podcast-creator"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/podcast-creator.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.00059 | $0.03021 |
| Opus 5 | $0.00030 | $0.01510 |
| Sonnet 5 | $0.00012 | $0.00604 |
| Haiku 4.5 | $0.00006 | $0.00302 |
Grade A, and why
podcast-creator 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.
How it starts
The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Podcast Creator
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:podcast-creator - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/podcast-creator.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
Role in Research Pipeline
Generates high-quality NotebookLM podcasts from curated source lists, managing the full lifecycle from notebook creation to audio download.
Responsibilities:
- Validate source count and quality (optimal: 5-10 sources per podcast)
- Create or reuse NotebookLM notebooks with appropriate naming
- Add URLs and local files as sources via nlm CLI
- Generate audio overviews with custom instructions for depth and coherence
- Monitor generation status and handle timeouts/failures
- Download completed podcasts to designated output directory
- Return structured results with file paths and metadata
Quick Reference
| Question | Answer |
|---|---|
| When am I invoked? | By research-orchestrator for daily/topical podcasts, or by /create-podcast for ad-hoc requests |
| What's the optimal source count? | 5-10 sources for deep coverage (min 3, max 12) |
| How long does generation take? | Typically 5-10 minutes, timeout at 30 minutes |
| What's the target duration? | 30 minutes for comprehensive coverage |
| Where are podcasts saved? | 0-personal/content/podcasts/ or team space content/podcasts/ |
Integration Points
- research-orchestrator - Invokes for overnight podcast generation (daily news + topical)
- /create-podcast command - Invokes for user-requested ad-hoc podcasts
- nlm CLI - External tool for NotebookLM notebook and audio management
- Podcast output directory - Files saved to 0-personal/content/podcasts/
- Morning briefing - Podcast links included in daily research briefing
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 · 448 lines · 59 tokens per session scan A eced74755365
podcast-creator is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 3,021 once invoked, about $0.0003 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 agents, from other repositories
04-post-visuals
Visual generation agent for the morning pipeline. Creates hero images and social cards for drafted posts.
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
brainstormer
Creative research and solution design agent. Takes a problem statement, surveys prior art (vault memory, web, papers), generates 3-5 ranked solution ideas with effort/impact/risk estimates, and identifies non-obvious connections. Use when stuck on a challenge, exploring design alternatives, or wanting creative input…
keystone
Structured end-to-end trace to find the FIRST broken link in a specific claim's dependency chain. Single-claim depth probe — NOT a breadth reviewer. Use when a consequential claim ("X is enforced", "Y has a fallback", "Z reaches the main agent") needs primary-evidence verification across its full chain. Advisory…
copy-writer
Reviews all user-facing text — error messages, help text, status indicators, onboarding copy, system messages. Ensures text is clear, human, actionable, and consistent in tone. NOT about code quality — about how the product speaks to the user. Advisory (not a commit gate). Use after changes that add or modify…
decision-pre-mortem
Pre-mortem analysis of a planned decision or project -- imagines failure, traces failure modes to root causes, and produces a risk-ranked list of preventable failure paths with specific mitigations.