A command-line toolkit for working with podcasts and their transcripts. Podwise can search shows and episodes, monitor releases, and answer questions about podcast content.

It helps find episodes, discover popular content, extract insights, process podcast and YouTube links, and work with local audio or video files.

It removes the need to manually search episodes or listen through recordings to find specific information.

podwise — Skill for Claude Code and Codex by memorysaver/dotfiles

Install

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.

Any agent

npx skills add memorysaver/dotfiles --skill podwise

Clone the repo

git clone --depth 1 https://github.com/memorysaver/dotfiles

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/memorysaver/dotfiles/podwise/github.svg)](https://agentmods.dev/skills/memorysaver/dotfiles/podwise)

Your own site

<a href="https://agentmods.dev/skills/memorysaver/dotfiles/podwise"><img src="https://agentmods.dev/badge/skills/memorysaver/dotfiles/podwise/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/memorysaver/dotfiles/podwise"><img src="https://agentmods.dev/badge/skills/memorysaver/dotfiles/podwise.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 149 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,292 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 89% copy Near-identical to another mod in the catalogue.

Token cost

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.1	$0.00149	$0.01292
Opus 5.5	$0.00060	$0.00517
Sonnet 5.5	$0.00030	$0.00258
Haiku 4.5	$0.00015	$0.00129

Measured 1mo ago against content hash 9000f7968cfe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

podwise 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 1mo 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.

Origin

This is a copy

89% identical to podwise — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/skills/podwise/SKILL.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Podwise

Podwise skills help you get more out of every podcast you listen to.

References

Load these files when needed — do not load all of them upfront:

references/cli.md — full CLI command reference. Load before running any podwise command or looking up flags and syntax.
references/installation.md — installation and API key setup. Load if podwise is not installed or not configured.
references/taste.md — the taste profile format and conventions this skill expects. Load when you need to interpret or create a listener profile.

Environment Check

Before running any workflow, verify the CLI is available:

podwise --help
podwise config show

If podwise is not installed or the API key is missing, load references/installation.md and stop until setup is complete.

CLI Reference

Before running any podwise command, load references/cli.md as the source of truth for exact flags, subcommands, and examples. Do not guess command syntax from memory.

First-Time Setup

If the project's taste.md does not exist, suggest running the refine-taste workflow before any other workflow. Other workflows will still run without it, but their outputs will not be personalised.

Workflow Routing

workflows/refine-taste.md

"Set up my Podwise profile"
"Tell me about my listening habits"
"I want to personalise my recommendations"
"Refine my taste profile"
Running any other workflow for the first time and references/taste.md does not exist

workflows/catch-up.md

"I haven't listened in a while, catch me up"
"What did I miss this week?" / "What's new from my podcasts?"
"Help me clear my backlog" / "Too many unheard episodes"
"Show me what's new from the shows I follow"
"Triage my podcast queue"

workflows/weekly-recap.md

"Give me a recap of this week's listening"
"What did I listen to this week?" / "Summarise my week in podcasts"
"Send me a weekly digest" / "What were the highlights from this week?"
"I want a summary of what I've been listening to lately"

Read the full file on GitHub · 129 lines

Files

What ships with it

11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

1mo ago First seen · 129 lines · 149 tokens per session scan A 9000f7968cfe

Subscribe to this mod's changes

podwise is a skill published in the GitHub repository memorysaver/dotfiles (7 stars, last pushed 8d ago), licensed MIT. It adds 149 tokens to every session and 1,292 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to podwise, differing in 5 lines, and is treated as a copy.

Research

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens