What is post-call-recap?

A meeting follow-up tool for Megamind call data, Slack messages, and call transcripts. It creates a recap of a client call.

Use it to write call summaries, follow-up drafts, next-step lists, and recaps formatted for Slack.

It removes the need to gather recent call and Slack context manually before writing a follow-up. It also helps turn unclear discussion into assigned next steps when ownership is stated.

post-call-recap — Skill for Claude Code and Codex by orchidautomation

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 orchidautomation/pluxx --skill post-call-recap

Clone the repo

git clone --depth 1 https://github.com/orchidautomation/pluxx

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/orchidautomation/pluxx/post-call-recap/github.svg)](https://agentmods.dev/skills/orchidautomation/pluxx/post-call-recap)

Your own site

<a href="https://agentmods.dev/skills/orchidautomation/pluxx/post-call-recap"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/post-call-recap/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/orchidautomation/pluxx/post-call-recap"><img src="https://agentmods.dev/badge/skills/orchidautomation/pluxx/post-call-recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 229 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.

Model	Per session	Once invoked
Fable 5.1	$0.00039	$0.00229
Opus 5.5	$0.00016	$0.00092
Sonnet 5.5	$0.00008	$0.00046
Haiku 4.5	$0.00004	$0.00023

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

Security

Grade A, and why

post-call-recap 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 2mo 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.

example/megamind/skills/post-call-recap/SKILL.md · 27 lines

What it actually says

Megamind Post-Call Recap

Generate a post-call recap from the latest Megamind transcript, recent Slack context, and any extra user context.

Workflow

Identify the client.
Pull in parallel:
- get_client_pulse(client_id, days=3)
- get_messages(client_id, days=3)
Fetch the most recent call transcript with get_call_transcript(call_id).
If multiple same-day calls exist, fetch them all in parallel and use the most complete one.
Ask the user for any missing offline context before drafting.
Produce a recap with Summary and Next Steps.

Output Rules

Use the client's own terminology when possible.
Keep bullets short and specific.
Cross-reference Slack for names, deliverables, and prior context.
Assign clear ownership in Next Steps when the transcript supports it.

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.

2mo ago First seen · 27 lines · 39 tokens per session scan A 11db7c943080

Subscribe to this mod's changes

post-call-recap is a skill published in the GitHub repository orchidautomation/pluxx (5 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 229 once invoked, about $0.0002 per session on Opus 5.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.

Writing and docs

post-call-recap next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
post-call-recaporchidautomation/pluxx	Skill	5	1mo ago	MIT	A	39	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	today	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	today	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	314k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code