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/modem-dev/podguy/podguy-post-productionnpx skills add modem-dev/podguy --skill podguy-post-productiongit clone --depth 1 https://github.com/modem-dev/podguyWhat 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.00064 | $0.02717 |
| Opus 5 | $0.00032 | $0.01358 |
| Sonnet 5 | $0.00013 | $0.00543 |
| Haiku 4.5 | $0.00006 | $0.00272 |
Grade A, and why
podguy-post-production 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 3d 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
podguy Post Production
This repository is meant to be operated through pi from the repo root.
Goal
Help with repeatable post-recording podcast editing for any podcast or video podcast.
Use this workflow when the user wants any of the following:
- analyze a new episode recording, draft export, or preview media file
- generate a transcript for the current cut of the episode
- prepare transcript artifacts for long-context editorial review
- find likely interstitial or inserted-content timecodes in video episodes
- propose YouTube or podcast chapter markers
- review the episode for cuts, highlights, clips, weak sections, and publishing assets
- cut/export selected clip candidates for TikTok, Reels, YouTube Shorts, trailers, or social review
Podcast profile
Prefer show-specific context from podguy.toml when it exists. If only podcast.toml exists, use that as a compatible profile file.
Use profile fields such as:
show_nameshow_slughoststoneaudiencechapter_stylepreferred_review
Do not assume a specific show, hosts, audience, tone, domain, or episode naming pattern unless the user or profile provides it.
If profile context is missing, only ask for it when it affects the requested deliverable. For example, chapters usually do not need a full show profile; publishable show notes might.
Natural-language UX
Assume the user will ask in plain English and may not know or remember slash commands.
Prompt templates such as /prepare-analysis, /phase1, /full-review, /chapters, and /cuts are optional shortcuts for power users, not required vocabulary.
When the request is ambiguous, ask one short clarifying question before deciding how much work to do.
Use this default clarification:
- quick pass = optional video scan + transcript + prepared transcript artifacts + short summary
- full review = quick pass + chapters + clips + cuts + show notes + quotes + proper noun review
If the user already clearly asked for a specific deliverable, do that directly instead of asking.
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.
- 3d ago First seen · 354 lines · 64 tokens per session scan A e2d71dedb6ed
podguy-post-production is a skill published in the GitHub repository modem-dev/podguy (47 stars, last pushed 17d ago), licensed MIT. It adds 64 tokens to every session and 2,717 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…