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 skills add Doris-Labs/sales-skills --skill post-call-followupgit clone --depth 1 https://github.com/Doris-Labs/sales-skillsWrote 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/doris-labs/sales-skills/post-call-followup)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/post-call-followup"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/post-call-followup/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/skills/doris-labs/sales-skills/post-call-followup"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-skills/post-call-followup.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.00059 | $0.01058 |
| Opus 5.5 | $0.00024 | $0.00423 |
| Sonnet 5.5 | $0.00012 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
post-call-followup 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Call Follow-Up
Purpose
Turn a just-finished call into three artifacts: a recap email the buyer actually wants, clear mutual next steps, and a CRM update that keeps the deal honest.
Inputs
- What was discussed (transcript, notes, or your recollection)
- Who was on the call and their role
- The deal's current stage and what you're trying to advance
Method
-
Extract the spine of the call. Work this checklist so nothing gets dropped:
- Pains named — the problems the buyer stated, in their words.
- Value landed — which of your points they reacted to (and which fell flat).
- Objections raised — concerns, hesitations, and who raised them.
- Commitments — both sides: what you owe, what they owe. (See the rule below.)
- Next step — the single agreed action, with an owner and a date.
- People — anyone new mentioned, their role, and whether they're for/against.
-
Draft the recap email in the buyer's language — lead with their stated problem, mirror their words, make the next step a single clear ask. Keep it under 150 words.
-
Write next steps as
owner + action + date. No orphaned tasks; if a step has no date, it isn't a commitment yet — chase the date. -
Produce the CRM update. Map the call to concrete fields, and flag — don't silently overwrite — anything the call contradicts:
CRM field Update from the call Stage Advance only if the exit criteria were actually met; otherwise hold + note why. Next step / next step date The agreed action + date from step 3. Close date Adjust only if the buyer gave a real date signal; flag if it now looks unrealistic. MEDDPICC slots Update Champion / Economic buyer / Metrics / Decision process as the call revealed them. Contacts / roles Add new stakeholders; update influence/sentiment. ⚠️ Contradictions List any field the call disproves (e.g. "stage = Negotiation but no economic buyer engaged") for the rep to resolve.
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 · 95 lines · 59 tokens per session scan A e701ed99a937
post-call-followup is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 1,058 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.
post-call-followup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| post-call-followupDoris-Labs/sales-skills | Skill | 3 | 5mo ago | MIT | A | 59 | Claude Code |
| lynquGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 40 | Claude Code, Codex |
| lynqu-sales-followupGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 39 | Claude Code, Codex |
| lynqu-deal-deskGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 48 | Claude Code, Codex |
| lynqu-event-blitzGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 47 | Claude Code, Codex |
| lynqu-lead-managementGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 40 | Claude Code, Codex |
| lynqu-outreachGravisun/lynqu-ai-toolkit | Skill | 6 | 11d ago | none | A | 41 | Claude Code, Codex |