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 First-Touch-Inc/firsttouch-agent-skill-packs --skill post-demo-followupgit clone --depth 1 https://github.com/First-Touch-Inc/firsttouch-agent-skill-packsWrote 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/first-touch-inc/firsttouch-agent-skill-packs/post-demo-followup)<a href="https://agentmods.dev/skills/first-touch-inc/firsttouch-agent-skill-packs/post-demo-followup"><img src="https://agentmods.dev/badge/skills/first-touch-inc/firsttouch-agent-skill-packs/post-demo-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/first-touch-inc/firsttouch-agent-skill-packs/post-demo-followup"><img src="https://agentmods.dev/badge/skills/first-touch-inc/firsttouch-agent-skill-packs/post-demo-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.00097 | $0.01457 |
| Opus 5 | $0.00048 | $0.00728 |
| Sonnet 5 | $0.00019 | $0.00291 |
| Haiku 4.5 | $0.00010 | $0.00146 |
Grade A, and why
post-demo-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 12d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-Demo Follow-Up
Outcome: The meeting momentum survives contact with the calendar. Same-day follow-up to the attendees, expansion to the stakeholders who were not in the room, and a scheduled momentum touch - all drafted from what actually happened in the meeting, all approved before anything sends.
First-run onboarding gate
Before running this skill for the first time in a workspace, load ../../references/onboarding.md and complete the onboarding questions. Do not proceed until you know: LinkedIn account type (free/basic = no connection notes; recommend 10 connection requests/day and never exceed the FirstTouch max of 20/day; Sales Navigator/Premium = connection notes available; recommend 20 connection requests/day and never exceed the FirstTouch max of 30/day), HubSpot access (MCP, service key/private app token, HubSpot list only, or none), and which play the user wants to run. If HubSpot is unavailable, run from user-provided meeting details instead of CRM context.
When to use
- "We just finished the demo with Acme"
- Multi-threading an account right after a meeting
- A demo no-show needs recovering without guilt-tripping
- Three days post-demo and the thread has gone quiet
Step-by-step
1. Gather the meeting context
With HubSpot connected: pull the meeting record, attendees, deal stage, and recent notes for the contact/deal. Without HubSpot: ask the user for the essentials.
Either way, confirm these five inputs before drafting - and never fabricate meeting details; if something is missing, ask:
- Who attended (names/roles) and who was invited but absent
- The 1-2 pains that actually resonated
- What was promised (recap, pricing, security doc, intro)
- The agreed next step and its date, if one exists
- Known stakeholders NOT in the meeting (economic buyer, technical lead)
2. Draft the follow-up set
Draft all applicable pieces in one pass using firsttouch-messaging quality gates; the user picks which to send:
- Same-day buyer follow-up (email or LinkedIn message to the main attendee): recap in one line, the promised item, the agreed next step with date. No new pitch.
- Champion thank-you (LinkedIn message): short, human, references one specific moment from the call. Builds the relationship, asks for nothing.
- Stakeholder expansion (connection request + opener to 1-2 people who were not in the room): references the live evaluation without leaking details - "We're working with {champion} on {topic}; wanted to connect since this touches your team." Never make the champion look bypassed - when in doubt, ask the champion first.
- 3-day momentum touch (queued, sends only if no reply): drafted against the stored promise from step 1 - deliver the promised item or answer the open question that came up in the meeting. Never a generic "just checking in."
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.
- 12d ago First seen · 77 lines · 97 tokens per session scan A c3e87f504db6
post-demo-followup is a skill published in the GitHub repository First-Touch-Inc/firsttouch-agent-skill-packs (5 stars, last pushed 2mo ago), licensed MIT. It adds 97 tokens to every session and 1,457 once invoked, about $0.0005 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-31.
Other skills, from other repositories
linkedin-mcp
Use LinkedIn data for profile, company, job, post, feed, inbox, recruiting, and outreach work through the bundled LinkedIn MCP server. Use only for an explicit LinkedIn request.
social-carousel
A three-card social media carousel where one headline continues across three square images. The cards can include a brand mark, numbering, a visual focus, and a call to action.
linkedin-content
Use when writing the actual words of one LinkedIn feed post — turning a raw idea, story or asset into ready-to-paste copy: a text post, a document/carousel cover with slide copy and caption, or a short native-video script. Covers fixing a weak hook, reformatting a wall of text for the mobile feed, and a CTA that…
sdr-humanizer
Transform AI-generated sales messages into natural, human-like conversations that build trust and rapport.
gr-social-distill
A content-repurposing workflow that turns one published blog post into several social-media formats, including an X thread, a Xiaohongshu post, a LinkedIn carousel, and a dev.to or Zenn article.
supermemory
Semantic memory layer powered by vector search. Store, recall, and connect conversation insights across all customer interactions.