post-call

post-call is a skill for Claude Code, Codex from chacosoldier/compabob. It costs 51 tokens per session (334 once invoked), scanned A, original, MIT.

A meeting follow-up workflow that turns a call or meeting into a written record of decisions, assigned actions, new information, and the next follow-up. It can update notes about attendees, projects, and the meeting itself after approval.

In plain words
What is it for?
Use it after a meeting when you have notes or a transcript and need to record decisions, assign follow-ups, update people or project notes, and review proposed file changes.
Why use it?
Important agreements and responsibilities often disappear into memory or scattered notes after a call. This workflow keeps them available and connected to the relevant project information.

Skill for Claude CodeCodex

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/chacosoldier/compabob/post-call
Any agent
npx skills add chacosoldier/compabob --skill post-call
Clone the repo
git clone --depth 1 https://github.com/chacosoldier/compabob

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.

agentmods badge for post-call

README.md
[![agentmods](https://agentmods.dev/badge/skills/chacosoldier/compabob/post-call.svg)](https://agentmods.dev/skills/chacosoldier/compabob/post-call)
Your own site
<a href="https://agentmods.dev/skills/chacosoldier/compabob/post-call"><img src="https://agentmods.dev/badge/skills/chacosoldier/compabob/post-call.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 334 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.00051 $0.00334
Opus 5 $0.00026 $0.00167
Sonnet 5 $0.00010 $0.00067
Haiku 4.5 $0.00005 $0.00033

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

Security

Grade A, and why

post-call 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 5d 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.

.claude/skills/post-call/SKILL.md · 27 lines

What it actually says

Post-Call Debrief

Close the loop that /meeting-prep opens. Turn a finished conversation into durable vault state.

Steps

  1. Gather. Ask the user for the raw account of the call, or work from notes or a transcript they provide.
  2. Extract four things:
    • Decisions — what was actually decided.
    • Action items — who owes what, by when. Run these through the second-brain task intake gate so they do not duplicate existing tasks.
    • New information — anything that changes what the vault knows about a person, account, or project.
    • Follow-up — the next touchpoint, if any.
  3. Update the vault.
    • Write or update the meeting note vault/Meetings/YYYY-MM-DD-<slug>.md.
    • Update each attendee's vault/People/<Name>.md: append to ## Interactions, refresh their current focus.
    • Update the relevant project or pipeline note.
  4. Confirm the changes with the user before writing anything that overwrites existing content.

Output

A short summary first: the one decision or change that matters most. Then the meeting note content for review. Then the list of vault files that will be created or updated, for approval.

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. 5d ago First seen · 27 lines · 51 tokens per session scan A 8f26273013ef

Subscribe to this mod's changes

post-call is a skill published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 334 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-30.