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 getaero-io/gtm-eng-skills --skill luma-event-campaigngit clone --depth 1 https://github.com/getaero-io/gtm-eng-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/getaero-io/gtm-eng-skills/luma-event-campaign)<a href="https://agentmods.dev/skills/getaero-io/gtm-eng-skills/luma-event-campaign"><img src="https://agentmods.dev/badge/skills/getaero-io/gtm-eng-skills/luma-event-campaign/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/getaero-io/gtm-eng-skills/luma-event-campaign"><img src="https://agentmods.dev/badge/skills/getaero-io/gtm-eng-skills/luma-event-campaign.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.00055 | $0.00840 |
| Opus 5.5 | $0.00022 | $0.00336 |
| Sonnet 5.5 | $0.00011 | $0.00168 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
luma-event-campaign 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 22d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Luma event campaign (DRAFT)
When to use
You have (or are creating) a Luma event and need a repeatable campaign system: guest acquisition → enrichment → messaging → staged outreach → registration hygiene. Not for one-off "write me an invite tweet."
Non-negotiables
- Keep outbound campaigns paused until a human approves sends.
- Pilot enrich on ≤10 rows before full waterfall.
- No invented speaker bios, titles, or company facts.
- Templates use placeholders (
{{event_name}},{{city}},{{speaker_1}}). - Prefer systems language: skills, plays, webhooks, score → approve → door — not "blast the list."
Inputs
| Input | Required | Notes |
|---|---|---|
| Luma event URL or export CSV | yes | At least name, email, status |
| ICP / TAL sheet (domains) | no | Boosts scoring |
| Brand voice notes | no | Else use templates/voice.md |
| Sequencer (Lemlist/Instantly/etc.) | no | Stage paused campaign only |
Standard flow
1. Frame the system
Say out loud (or in the run log):
- Source of truth for guests (Luma)
- Enrich + score path
- Messaging artifacts (invite email, LI DM, social)
- Outreach object (paused)
- Inbound sync (registration webhook — see
luma-inbound-webhook-enrich)
2. Guest list hygiene
- Export or API-pull guests.
- Normalize emails; drop empties; flag duplicates.
- Map ticket/status: pending / approved / waitlist / checked_in.
- Write
guests.normalized.csv.
3. Enrich + score (pilot first)
- Run a 10-row pilot enrich (email validation + LinkedIn URL + title/company).
- Score segments:
hot/warm/low/skipusing ICP + TAL + seniority. - Full run only after pilot lookback.
- Write
guests.scored.csv.
4. Messaging pack
Use templates in templates/:
invite-email.md— HubSpot or transactional invitelinkedin-dm.md— short DM, no hype wordssocial-announcement.md— X/LinkedIn announcementspeaker-bio.md— only from verified sources
Fill placeholders; human-edit before publish.
What ships with it
6 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.
- 22d ago First seen · 100 lines · 55 tokens per session scan A fc6e0a720980
luma-event-campaign is a skill published in the GitHub repository getaero-io/gtm-eng-skills (66 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 840 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-22.
Other skills, from other repositories
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
delete-project
This skill should be used when the user asks to "delete a project", "remove a project", or wants to permanently delete a registered project and all its data from the server.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
funding-signal-monitor
Monitor web sources for Series A-C funding announcements. Aggregates signals from TechCrunch, Crunchbase (via web search), Twitter, Hacker News, and LinkedIn. Filters by stage, amount, and industry. Returns qualified recently-funded companies ready for outreach.
signal-scanner
Detect buying signals across TAM companies and watchlist personas. Three-phase architecture: (1) free diff-based signals from existing data (headcount growth, tech stack changes, funding rounds), (2) Apify-powered signals (job postings, LinkedIn content analysis, profile changes), and (3) post-processing with dedup…