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 swan-gtm/gtm-skills --skill post-meeting-executiongit clone --depth 1 https://github.com/swan-gtm/gtm-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/swan-gtm/gtm-skills/post-meeting-execution)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/post-meeting-execution"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/post-meeting-execution/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/swan-gtm/gtm-skills/post-meeting-execution"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/post-meeting-execution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Output Handling · line 179 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
- medium Excessive Agency · line 221 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00124 | $0.03711 |
| Opus 5 | $0.00062 | $0.01855 |
| Sonnet 5 | $0.00025 | $0.00742 |
| Haiku 4.5 | $0.00012 | $0.00371 |
Grade A, and why
post-meeting-execution 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 9d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-meeting execution
Template placeholders
Replace every {{...}} before enabling. See the setup checklist reference for the full setup list.
{{MEETING_OWNER}}— Person whose meetings this skill processes (one instance per person){{MEETING_NOTES_TOOL}}— Your meeting-notes tool (e.g. Circleback, Fireflies, Gong){{CRM}}— Your CRM (e.g. HubSpot, Attio, Salesforce){{REVIEW_CHANNEL}}— Slack channel where all post-meeting outputs post for review{{INTERNAL_DOMAIN}}— Your company email domain, to tell internal from external attendees{{FOLLOWUP_SCENARIOS_SKILL}}— Sub-skill: meeting-outcome categories, classification logic, per-category email frameworks{{VOICE_GUIDE_SKILL}}— Sub-skill: the owner's tone, formatting, greeting style, approved links{{LEAD_SCORING_SKILL}}— Sub-skill: your lead scoring & qualification methodology{{ENTERPRISE_ACV_THRESHOLD}}— Deal size above which an account gets full sales treatment vs. self-serve (default: $20K){{SALES_ACTIVE_TAG}}— Workspace tag marking accounts with a live sales conversation{{METRICS_LOG}}— Optional: spreadsheet/event log where external meetings are recorded for GTM metrics
Overview
After every meeting involving {{MEETING_OWNER}}, run a structured workflow in two phases:
- Deal creation decision — qualification scoring, human confirmation, contact/stakeholder loading
- Follow-up email — classify the outcome, draft in the owner's voice, send for approval
Non-blocking errors: memory, enrichment, and {{CRM}} write failures are non-blocking — log the error in the review item and continue; a failed step is never a reason to skip subsequent steps. The only blocking failure is a missing meeting record (Step 1).
Step 1 — Pull Meeting Context
Retrieve the full record from {{MEETING_NOTES_TOOL}}: summary, full transcript, action items, attendees (names, titles, companies), any logged decisions. If your notes tool auto-emails attendees the summary and recording, do NOT duplicate that in the follow-up email.
What ships with it
1 file 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.
- 9d ago First seen · 222 lines · 124 tokens per session scan A 61b39df9bb61
post-meeting-execution is a skill published in the GitHub repository swan-gtm/gtm-skills (153 stars, last pushed 2d ago), licensed MIT. It adds 124 tokens to every session and 3,711 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.