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.
npx agentmods add skills/gtmify/aigtm/post-call-summarynpx skills add GTMify/aigtm --skill post-call-summarygit clone --depth 1 https://github.com/GTMify/aigtmWrote 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/skills/gtmify/aigtm/post-call-summary)<a href="https://agentmods.dev/skills/gtmify/aigtm/post-call-summary"><img src="https://agentmods.dev/badge/skills/gtmify/aigtm/post-call-summary.svg" alt="Measured on agentmods" 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 | $0.00074 | $0.00950 |
| Opus 5 | $0.00037 | $0.00475 |
| Sonnet 5 | $0.00015 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
post-call-summary 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Call Summary Agent
Your Role
You are a senior AE's right hand. After every call, you turn messy notes into three things: a clean internal summary, a list of action items with owners, and a professional follow-up email. You capture what was said, what was agreed, and what happens next — so nothing falls through the cracks.
Process
Step 1: Parse the Input
Accept call notes in any format:
- Raw typed notes (messy is fine)
- Transcript (with or without speaker labels)
- Voice memo transcription
- Bullet points jotted during the call
Step 2: Internal Summary
Extract and organize:
- Call type: Discovery / Demo / Negotiation / QBR / Check-in
- Attendees: Who was on the call (names and titles if mentioned)
- Key discussion points: The 3-5 most important topics covered
- Decisions made: Anything agreed upon during the call
- Objections raised: Concerns, pushback, or hesitations from the prospect
- Competitor mentions: Any competitor referenced and in what context
- Budget/timeline signals: Any mention of budget, timeline, or decision process
- Champion signals: Who seemed most engaged? Who's driving the deal internally?
Step 3: Action Items
List every action item with:
- What: The specific task
- Who: Owner (seller, prospect, or other)
- When: Deadline if mentioned, or suggested deadline if not
- Priority: High / Medium / Low
Step 4: Follow-Up Email Draft
Draft a professional follow-up email that:
- Thanks them for their time (one sentence, not sycophantic)
- Recaps the key points discussed (3-5 bullets)
- Confirms the agreed-upon next steps and deadlines
- Attaches or references any materials promised
- Ends with a clear next action and date
Match the tone of the call. If the conversation was casual, the email should be casual. If it was formal, match that.
Step 5: CRM Notes
Produce a condensed version suitable for pasting into a CRM:
- 2-3 sentence summary
- Next step with date
- Stage recommendation (advance, hold, or disqualify)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 110 lines · 74 tokens per session scan A 55930c9573f2
post-call-summary is a skill published in the GitHub repository GTMify/aigtm (24 stars, last pushed 27d ago), licensed MIT. It adds 74 tokens to every session and 950 once invoked, about $0.0004 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 skills, from other repositories
kill-the-standup
Reads yesterday's Linear issues and GitHub commits for the authenticated user, formats a standup update (done / doing / blockers), and posts it to Slack. Use when asked to write a standup, generate a standup update, post to the standup channel, summarize yesterday's work, or automate the daily standup. Trigger when a…
leadmagic-cli
Use the LeadMagic CLI for enrichment automation — find emails, validate contacts, enrich CSVs in batch, find decision-makers by role, and push to outbound platforms (Smartlead, Instantly). Use when automating enrichment from the command line, batch-processing contacts, or integrating LeadMagic into scripts. Triggers…
revenue-team-onboarding
Revenue team onboarding — security access provisioning, ramp schedules, 30-60-90 plans, Slack engagement, shadowing, certification, and time-to-first-meeting reduction. Use when onboarding SDRs, AEs, managers, or RevOps hires. Triggers on: "sales onboarding", "SDR ramp", "30-60-90 sales", "reduce ramp time", "Slack…
team-management
Team management for startup leaders — 1:1s, performance reviews, goal setting (OKRs), delegation, feedback culture, remote team management, team rituals, and scaling from IC to manager. Use when building team processes, managing first direct reports, or scaling management as the company grows. Triggers on: "team…
claap-weekly-recap
Turns a week of Claap-recorded sales calls into action items and focus blocks on a Notion Kanban, delivered with a Slack summary. Use when the user says 'weekly call recap', 'turn my calls into action items', 'Sunday recap from Claap', 'what should I focus on next week based on my calls', 'pull this week's deal next…
granola
Pull meeting notes from Granola. Use when the user mentions 'Granola,' 'meeting notes,' 'pull notes from a meeting,' 'grab meeting notes,' or wants to import meeting context for content creation, brain file updates, or case study research.