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 conference-meeting-cardsgit 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/conference-meeting-cards)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/conference-meeting-cards"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/conference-meeting-cards/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/conference-meeting-cards"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/conference-meeting-cards.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.00152 | $0.01881 |
| Opus 5.5 | $0.00061 | $0.00752 |
| Sonnet 5.5 | $0.00030 | $0.00376 |
| Haiku 4.5 | $0.00015 | $0.00188 |
Grade A, and why
conference-meeting-cards 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 25d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conference meeting cards
Template placeholders
Replace every {{...}} before enabling. See the setup checklist reference for the full setup list.
{{CARD_OWNER}}- The person the cards are written for (usually the seller walking the floor){{CRM}}- Your CRM (e.g. HubSpot, Attio, Salesforce) and the field names for deal amount, stage, next step, and close date{{STAGE_LABELS}}- Your CRM stage identifiers mapped to the human labels that should print on a card{{MEETING_NOTES_TOOL}}- Your meeting-notes or call-recording tool (e.g. Circleback, Gong, Fireflies), used as the next-step fallback{{NEXT_STEP_LOOKBACK_DAYS}}- How far back to search meeting notes for a next step when the CRM field is empty (default: 60){{FULL_BRIEF_SKILL}}- Your full pre-call meeting-prep skill. This skill is the walking-floor card, not that brief.{{DESIGN_TOKENS}}- Your brand colors and type, if you have a design reference the template should follow{{OUTPUT_FOLDER}}- Where day files are saved (default:events/{event-slug}/meeting-cards/{YYYY-MM-DD}.html){{MAX_BULLETS}}- Deal-context bullets per card (default: 6, optional 7th for a real key risk){{BULLET_CHAR_CAP}}- Characters per bullet (default: 150){{EVENT_TEAM}}- Who receives the share link by DM for this event (a per-event list, asked for if not given)
Instructions
Load this skill when the ask is a walking-floor card, not a chat meeting-prep brief. For a full pre-call brief, use {{FULL_BRIEF_SKILL}} instead.
Voice is sales-first. One screen per meeting. No fluff.
Input required before research
You need the event name, the date or dates, and per meeting: time (or TBD), company (domain preferred), and attendee names. Location is optional. Recipients for the DM are a per-event list; ask who is attending this conference before sending. Do not scrape {{CARD_OWNER}}'s calendar unless they say to.
Procedure
- Normalize the event slug and the meeting list. Group by date. Keep {{CARD_OWNER}}'s order when times are TBD.
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.
- 25d ago First seen · 93 lines · 152 tokens per session scan A 00e797385482
conference-meeting-cards is a skill published in the GitHub repository swan-gtm/gtm-skills (181 stars, last pushed 3d ago), licensed MIT. It adds 152 tokens to every session and 1,881 once invoked, about $0.0006 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-09-23.
Other skills, from other repositories
webhook-subscriptions
Webhook subscriptions: event-driven agent runs.
k8s-workload-inventory
List Kubernetes workloads and namespaces — pods with their node, phase and readiness, plus events. Use when asked what is running, where it is running, what is failing, or for a general inventory of a cluster.
luma-event-insights
Starter skill for analyzing Lu.ma events, attendees, invites, and engagement signals from organizer-provided API access, exports, or manual event inputs. Use this when a template or workflow needs a repeatable path to turn Lu.ma event data into an organizer-ready analysis brief.
huawei-cloud-cce-kubernetes-event-analyzer
Query and analyze Kubernetes Events in Huawei Cloud CCE clusters. Trigger when users ask about CCE events, Kubernetes warning events, FailedScheduling, FailedMount, ImagePullBackOff, event patterns, historical events in LTS, or event-based diagnosis for a CCE cluster or namespace.
cairo-contract-authoring
Cairo smart-contract authoring on Starknet. Trigger on "write a contract", "create a contract", "implement this in Cairo", "add storage/events/interface", "compose components". Guides structure, security patterns, and component wiring.
backend-event-sourcing
Use this skill when the user says 'event sourcing', 'event store', 'event stream', 'event sourced', 'rehydrate from events', 'event replay', 'projection rebuild', 'event log', 'append-only log', 'event history'. This skill enforces: events as the single source of truth, current state derived from event replay…