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 skills/cdeistopened/skill-stack/podcast-blog-post-creatornpx skills add cdeistopened/skill-stack --skill podcast-blog-post-creatorgit clone --depth 1 https://github.com/cdeistopened/skill-stackWrote 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/skills/cdeistopened/skill-stack/podcast-blog-post-creator)<a href="https://agentmods.dev/skills/cdeistopened/skill-stack/podcast-blog-post-creator"><img src="https://agentmods.dev/badge/skills/cdeistopened/skill-stack/podcast-blog-post-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.00043 | $0.03205 |
| Opus 5 | $0.00022 | $0.01603 |
| Sonnet 5 | $0.00009 | $0.00641 |
| Haiku 4.5 | $0.00004 | $0.00320 |
Grade A, and why
podcast-blog-post-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 5d 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 — 387 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Podcast Blog Post Creator
Purpose
Transform podcast episodes into SEO-optimized blog posts that capture the energy and authenticity of the conversation in written form. The output is a narrative-driven explainer that introduces the guest, highlights their key insight, and provides actionable value to readers - all in a natural, conversational voice.
Core Philosophy: Good writing is a transfer of energy. The blog post should feel like the host is sitting across from you, telling you about a conversation they had that changed how they think about something important.
When to Use This Skill
Use this skill when you:
- Have a polished podcast transcript and want to repurpose it as written content
- Want to drive SEO traffic from blog readers to the full podcast episode
- Need to create a permanent, searchable record of the episode's key insight
- Want to build guest relationships by making them look good in writing
- Are looking to establish expertise in a specific topic area through long-form content
Do NOT use for:
- Quick social media captions (use social-content-creation skill instead)
- Episode summaries (this goes deeper than summary)
- Transcripts (this is narrative, not transcript)
Key Principles
The Angle
Your blog post focuses on one primary insight or paradox from the episode, not everything the guest discussed. This is crucial. A guest might touch on 5-7 big ideas. You pick one and go deep.
How to identify the angle:
- What's the most counterintuitive idea?
- What's the most helpful for your core audience?
- What's a surprising realization that contradicts conventional wisdom?
- What's the guest's own lived example that proves the point?
The Voice
Write in a conversational, authentic voice: warm, curious, and genuine. The host is the guide inviting the reader into a conversation that happened.
Tone markers:
- Uses "I" and "we" naturally
- Asks genuine questions (not rhetorical)
- Tells stories and uses metaphors
- Focuses on the human element, not abstractions
- Doesn't preach or lecture
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.
- 5d ago First seen · 387 lines · 43 tokens per session scan A 7a39f911342e
podcast-blog-post-creator is a skill published in the GitHub repository cdeistopened/skill-stack (28 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 3,205 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…