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/squared-lemons-ltd/podmule-plugin/episode-writeupnpx skills add Squared-Lemons-Ltd/podmule-plugin --skill episode-writeupgit clone --depth 1 https://github.com/Squared-Lemons-Ltd/podmule-pluginWrote 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/squared-lemons-ltd/podmule-plugin/episode-writeup)<a href="https://agentmods.dev/skills/squared-lemons-ltd/podmule-plugin/episode-writeup"><img src="https://agentmods.dev/badge/skills/squared-lemons-ltd/podmule-plugin/episode-writeup.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.00595 |
| Opus 5 | $0.00022 | $0.00298 |
| Sonnet 5 | $0.00009 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
episode-writeup 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write up an episode
Titles, show notes, chapters and metadata are the assets that decide whether anyone finds an episode. PodMule generates them from the transcript, using the show's own stored prompts and brand voice — which is why the generation belongs on the server rather than in a chat window.
Prefer PodMule's own generation
enqueue_show_notes_generation runs the workspace's stored show-notes prompt with the show's brand voice and the episode transcript threaded in. Hand-writing show notes in the conversation instead produces something that reads fine and sounds nothing like the show — the brand voice is stored for a reason, and it does not travel into a chat prompt.
The same applies to enqueue_title_generation and enqueue_chapter_generation. Chapters in particular need transcript timestamps to be correct, which is not something to reconstruct by hand.
enqueue_full_episode_pipeline runs the whole sequence — transcribe, chunk, notes, titles, chapters, metadata — and is the right call for a freshly uploaded recording rather than four separate asks.
These are jobs, not answers
Every enqueue_* capability returns a job_id immediately and does the work in the background. Nothing is written when the call returns. get_job_status reports pending, running, completed or failed against that id.
Tell the user it has been kicked off rather than describing the output, and keep the job_id — without it there is no way to answer "is it done yet?" a few minutes later except guessing.
When the user wants to see before committing
generate_show_notes_preview produces show notes inline and returns them without writing to the episode. It also returns the resolved prompt — which key it used and whether it came from the workspace or the platform default — so a user who thinks the notes are off can see which prompt actually ran. That is usually the real question behind "these don't sound right".
Use the preview when the words are "preview", "show me", or "what would they look like". Use the enqueued generation when the user wants the episode updated.
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.
- 4d ago First seen · 39 lines · 43 tokens per session scan A 0eb397b20197
episode-writeup is a skill published in the GitHub repository Squared-Lemons-Ltd/podmule-plugin (0 stars, last pushed 16d ago), licensed MIT. It adds 43 tokens to every session and 595 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-31.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…