meeting-listen

meeting-listen is a command for Claude Code from punt-labs/prfaq. It costs 12 tokens per session (5,175 once invoked), scanned A, original, MIT.

A command that plays a completed meeting summary as a conversation between four named personas. Text-to-speech, or TTS, means software that reads text aloud; if it is unavailable, the dialogue is shown as text.

In plain words
What is it for?
Use it to listen to or read back a completed PR/FAQ meeting summary as an attributed debate between Wei, Priya, Alex, and Dana.
Why use it?
It turns a finished meeting summary into an easier-to-follow replay with different speakers and viewpoints.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the prfaq-dev plugin — 1 skill, 14 commands, 8 agents, 1 hook shipped together

Good fit Use it to listen to or read back a completed PR/FAQ meeting summary as an attributed debate between Wei, Priya, Alex, and Dana.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add punt-labs/prfaq
Claude Code
/plugin install prfaq-dev

Made for: Claude Code.

Or install prfaq-dev, the plugin that ships this one along with the rest of its 1 skill, 14 commands, 8 agents, 1 hook.

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 meeting-listen

README.md
[![agentmods](https://agentmods.dev/badge/commands/punt-labs/prfaq/meeting-listen/github.svg)](https://agentmods.dev/commands/punt-labs/prfaq/meeting-listen)
Your own site
<a href="https://agentmods.dev/commands/punt-labs/prfaq/meeting-listen"><img src="https://agentmods.dev/badge/commands/punt-labs/prfaq/meeting-listen/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.

agentmods 80×15 button for meeting-listen

Your own site · 80×15
<a href="https://agentmods.dev/commands/punt-labs/prfaq/meeting-listen"><img src="https://agentmods.dev/badge/commands/punt-labs/prfaq/meeting-listen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,175 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 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.1 $0.00012 $0.05175
Opus 5 $0.00006 $0.02587
Sonnet 5 $0.00002 $0.01035
Haiku 4.5 $0.00001 $0.00517

Measured 10d ago against content hash bdc2db3f7531, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

meeting-listen 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 10d 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.

plugin/commands/meeting-listen.md · 227 lines

How it starts

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

PR/FAQ Meeting Listen

Play back a completed meeting summary as a voiced conversation between four personas — Wei, Priya, Alex, and Dana — each speaking in their own voice. This is post-production: the meeting already happened, you're listening to the recording.

Prerequisites

Check whether mcp__plugin_vox_mic__unmute is available. Set a session flag:

  • Voiced mode — TTS is available. Voices will be used.
  • Text-only mode — TTS is not available. Tell the user: "TTS plugin not available — playing back as text-only transcript. Install punt-vox for voiced playback." Continue with all steps below, but skip all mcp__plugin_vox_mic__* calls. Print dialogue as attributed text instead.

Load ${CLAUDE_PLUGIN_ROOT}/skills/prfaq/references/plain-style.md — generative prose rules (no em dash, no negative parallelism, no corporate-register vocabulary, no value-claim filler, no explaining the document to the reader). The persisted meeting summary you read in step 2 already passed through prose_lint.py when it was written, but every line of dialogue you construct in step 6b, and every narrator or recap segment you author in step 7, is new text that is spoken or printed and never written to a file — apply every rule in plain-style.md to that new text before it is voiced or printed.

Steps

  1. Find the meeting summary. If $ARGUMENTS specifies a path, use it. Otherwise, use Glob to find meeting summaries with both patterns:

    • meetings/meeting-summary-*.md (interactive meetings)
    • meetings/meeting-hive-summary-*.md (hive meetings)

    Search from the user's current working directory (not the plugin root). If no results, broaden the search using **/meetings/meeting-summary-*.md and **/meetings/meeting-hive-summary-*.md to find meetings in subdirectories.

    If multiple exist, parse the YYYY-MM-DD date from each filename and choose the latest date. If there are multiple on the same date, choose the one with the highest numeric suffix (e.g., ...-2.md after the unsuffixed original). If none exist, tell the user: "No meeting summaries found. Run /prfaq:meeting or /prfaq:meeting-hive first."

Read the full file on GitHub · 227 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. 10d ago First seen · 227 lines · 12 tokens per session scan A bdc2db3f7531

Subscribe to this mod's changes

meeting-listen is a command published in the GitHub repository punt-labs/prfaq (25 stars, last pushed 8d ago), licensed MIT. It adds 12 tokens to every session and 5,175 once invoked, about $0.0001 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.