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.
git clone --depth 1 https://github.com/korovin-aa97/talkthrough-mcpWrote 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/commands/korovin-aa97/talkthrough-mcp/meeting-actions)<a href="https://agentmods.dev/commands/korovin-aa97/talkthrough-mcp/meeting-actions"><img src="https://agentmods.dev/badge/commands/korovin-aa97/talkthrough-mcp/meeting-actions/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.
<a href="https://agentmods.dev/commands/korovin-aa97/talkthrough-mcp/meeting-actions"><img src="https://agentmods.dev/badge/commands/korovin-aa97/talkthrough-mcp/meeting-actions.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00972 |
| Opus 5 | $0.00010 | $0.00486 |
| Sonnet 5 | $0.00004 | $0.00194 |
| Haiku 4.5 | $0.00002 | $0.00097 |
Grade A, and why
meeting-actions 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 7d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If no job_id was passed as an argument: call list_jobs() to find the right recording, or process_media(path) if the user gave a file path — then follow the workflow below with that job_id.
You are taking minutes from a recorded meeting processed by talkthrough as job
$ARGUMENTS. Audio-only jobs are expected here — frame tools are unavailable for
them, and that is fine.
Method
- get_transcript(job_id="$ARGUMENTS", format="segments") — walk the whole meeting (paginate via next_start_ms when truncated).
- Multi-person meeting without
speakerlabels on segments? Re-run process_media(path=, diarize=true, num_speakers=) — it adds S1/S2/… labels to the existing job without re-transcribing, and minutes with owners need them. - Attendees are listed above and the file is not processed yet (or you are re-running process_media anyway)? Pass vocabulary="<the attendees' names>" in that call — names survive transcription instead of degrading into look-alike words, and owner attribution depends on them.
- When segments carry speaker labels, map each label to a person before
writing minutes. Evidence: self-introductions ("hi, this is Vera"),
vocatives ("thanks, Tom"), the attendees list above — and, on video
jobs, the SCREEN. The screen check is MANDATORY on video jobs, not
optional: for EVERY label you map, call get_frames(job_id="$ARGUMENTS",
at_ms=<that label's longest_turn_at_ms from the roster>) and read the
meeting-app name plates, the recording's title card (who
started/organized it), and the active-speaker highlight BEFORE asserting
the mapping — vocative evidence alone mis-attributes (a remark spoken TO
Tom is routinely tagged as Tom speaking). Name spellings: STT
homophones lie (spoken "profit" vs on-screen "Prophet") — trust
OCR/frames over the transcript for names. State the mapping first (e.g.
S1 = Vera, S2 = Tom, S3 = unidentified) — never guess beyond the evidence. If the header carries speaker_names_pending_review, those names came from an older roster and are NOT active identities: use their stored context anchors to re-check each one. Confirm/replace only labels that are still current; remove stale labels with an explicit null patch. - Persist every defensible mapping with label_speakers(job_id="$ARGUMENTS", labels={"S1":""}, evidence={"S1":"<intro, frame, or attendee proof>"}). Never save OCR name_candidates directly: they are raw hints that may be UI text, a job title, or somebody else's name.
- Collect: action items (who committed to what), decisions (what was agreed), open questions (raised but unresolved). Keep exact quotes and t_ms for each.
- search(job_id="$ARGUMENTS", query="") to trace scattered follow-ups on one topic before summarizing it.
- If the job has video (a screen-share was recorded), attach visual evidence to items that reference the screen via get_moment(job_id="$ARGUMENTS", start_ms=..., end_ms=...).
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.
- 7d ago Changed · +3 lines 5b2ca6ecf1e5
- 11d ago First seen · 66 lines · 21 tokens per session scan A 8cd5978202c1
meeting-actions is a command published in the GitHub repository korovin-aa97/talkthrough-mcp (28 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 972 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.
Other commands, from other repositories
example-command
TODO — one-line description shown in the slash-command picker.
address-comments
Address my accepted PDF comments and resolve each one.
render_preview
Call the renderpreview MCP tool to compile the current LaTeX project and open the MagicTeX live preview. If the preview is already running this recompiles and refreshes it. When it finishes, tell me the workspace URL and the page count, and remind me I can select text on the PDF to leave comments.
search
Search across all project artifacts by keyword, document type, or requirement ID.
defer
Defer a task to the cleanest grid-energy window inside a deadline. Invoke this command automatically whenever the user signals a task is not time-critical — phrases like "do this later", "by tomorrow", "tonight", "overnight", "by EOD", "sometime this week", "when you have a moment", "remind me to", "queue this up"…
impact
Analyse the blast radius of a change to a requirement, decision, or design document.