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-booking-linksgit 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-booking-links)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/conference-booking-links"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/conference-booking-links/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-booking-links"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/conference-booking-links.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.00053 | $0.00916 |
| Opus 5.5 | $0.00021 | $0.00366 |
| Sonnet 5.5 | $0.00011 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
conference-booking-links 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 23d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conference booking links
Produce working links with verified availability for every host. Read references/cal-com.md for product sources and assets/booking-worksheet.md for inputs and results.
Establish the configuration
Reuse known event dates, venue timezone, location, hosts, daily meeting windows, duration, buffers, minimum notice, and personal commitments. Offer 20-minute meetings with 10 minutes afterward and two hours' notice only as a starting suggestion; use the user's preferences. Do not silently purchase a plan or create accounts.
Inspect existing event types and schedules to avoid duplicates or changing unrelated booking links. Prefer available Cal.com tools; otherwise use the logged-in browser. If access is missing, produce the configuration and remaining setup steps without claiming live completion.
Choose the hosting model from the intended meeting:
- One participant: personal event type.
- Separate links per teammate with standardized settings: managed template if available and authorized, otherwise consistent personal event types.
- All specified hosts must attend: collective.
- Any suitable available teammate may attend: round robin.
Check current plan capabilities. Do not substitute a different host model merely because a feature is unavailable.
Configure
- Connect each host's calendar through normal account authorization. Verify both calendars checked for conflicts and the destination for newly booked meetings. Do not copy credentials or assume a connected account checks every calendar.
- Create a dedicated conference availability schedule in the venue IANA timezone. Apply the exact permitted dates and hours, using the current date-range and date-override controls. Attach it to the event type. Keep availability outside the event closed; date overrides alone may leave recurring hours open.
- Set the title, duration, precise in-person meeting point, before/after buffers, minimum notice, and desired slot interval. Buffers do not necessarily set the spacing between displayed start times.
- Assign and activate the intended hosts when relevant. Verify each managed instance is usable; a shared template does not prove that every host's calendar connection or schedule works.
- Inspect existing Busy conflicts. Keep genuine meetings, sessions the person will attend, speaking slots, travel and assigned duties Busy. A broad “whole conference” reference hold may suppress all meetings even when the invitation is unanswered. Convert it to Free only when it is confirmed to be a reference hold and the user has authority and has authorized that change. Never clear real commitments just to produce slots.
- Preserve a useful rollback record: prior settings for modified event types, schedule IDs, host assignments and calendar selections. Store private operational IDs in the user's project, not this reusable skill.
What ships with it
3 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.
- 23d ago First seen · 49 lines · 53 tokens per session scan A 31fb7e899722
conference-booking-links is a skill published in the GitHub repository swan-gtm/gtm-skills (181 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 916 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-09-24.
Other skills, from other repositories
edgeos
Talk to the EdgeOS popup-village platform — read the event schedule in the village's local time, RSVP (after asking the person), list venues and who is going to an event, search the attendee directory and read the person's own Edge City profile through the Agent Village control plane (two scripts; the app reads EdgeOS…
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.