interview-brief

interview-brief is a skill for Claude Code, Codex from Squared-Lemons-Ltd/podmule-plugin. It costs 61 tokens per session (616 once invoked), scanned A, original, MIT.

A one-page preparation brief about a podcast interview guest, including their background and relevant past conversations on the show.

In plain words
What is it for?
It helps prepare for upcoming interviews by reviewing bookings, contact details, notes, social profiles, and previous episodes.
Why use it?
It helps the host avoid repeating questions and understand what the show's own records already say about the guest's subject.

Skill for Claude CodeCodex

Part of the podmule plugin — 5 skills, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/squared-lemons-ltd/podmule-plugin/interview-brief
Any agent
npx skills add Squared-Lemons-Ltd/podmule-plugin --skill interview-brief
Clone the repo
git clone --depth 1 https://github.com/Squared-Lemons-Ltd/podmule-plugin

Made for: Claude Code, Codex.

Or install podmule, the plugin that ships this one along with the rest of its 5 skills, 1 MCP server.

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.

agentmods badge for interview-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/squared-lemons-ltd/podmule-plugin/interview-brief.svg)](https://agentmods.dev/skills/squared-lemons-ltd/podmule-plugin/interview-brief)
Your own site
<a href="https://agentmods.dev/skills/squared-lemons-ltd/podmule-plugin/interview-brief"><img src="https://agentmods.dev/badge/skills/squared-lemons-ltd/podmule-plugin/interview-brief.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 616 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00061 $0.00616
Opus 5 $0.00030 $0.00308
Sonnet 5 $0.00012 $0.00123
Haiku 4.5 $0.00006 $0.00062

Measured 3d ago against content hash 3d8107d854ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

interview-brief 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.

plugins/podmule/skills/interview-brief/SKILL.md · 37 lines

How it starts

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

Brief me on this guest

The point of a guest brief is to stop the host asking a question the guest already answered two years ago, and to arrive knowing what the show's own back catalogue says about their subject. Everything here is read-only.

Start from the booking, or from the person

list_interviews gives upcoming bookings sorted by start time — the usual entry point for "who am I talking to next". Note its status semantics: confirmed stays confirmed after the scheduled time passes, so a confirmed booking in the list is not proof it is still ahead.

get_interview returns one booking in full: contact, show, times, timezones and notes. The notes are usually where the reason for the booking lives.

When the ask names a person rather than a booking, search_contacts matches on name, email or company, and get_contact returns their groups, social profiles and a preview of recent notes. list_contact_notes returns the complete note history — the preview truncates, so use the full list whenever the brief is meant to be thorough.

Have they been on before?

This is the part a general model cannot do and the part that makes the brief worth reading.

search_episodes accepts a guest name and finds prior appearances. search_knowledge may hold a guest page — PodMule accumulates one per recurring guest across every episode they appear in, which is a better starting point than re-reading three transcripts. get_knowledge_page returns it in full with citations back to the episodes.

If they are new to the show, say so explicitly. "First appearance" is useful information, and it is easy to leave a brief looking thin when it is actually complete.

What does the show already know about their subject?

Once you know the guest's territory, search_knowledge on that topic surfaces what the show has already concluded about it — from other guests, other episodes. That is where the non-obvious questions come from: the places where this guest's position will contradict, confirm or extend something already on record.

Read the full file on GitHub · 37 lines

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.

  1. 3d ago First seen · 37 lines · 61 tokens per session scan A 3d8107d854ae

Subscribe to this mod's changes

interview-brief is a skill published in the GitHub repository Squared-Lemons-Ltd/podmule-plugin (0 stars, last pushed 16d ago), licensed MIT. It adds 61 tokens to every session and 616 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-31.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 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