Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/YALC-the-GTM-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/fullenrich-event-attendees/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-systemWrote 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/othmane-khadri/yalc-the-gtm-operating-system/fullenrich-event-attendees)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/fullenrich-event-attendees"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/fullenrich-event-attendees/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/othmane-khadri/yalc-the-gtm-operating-system/fullenrich-event-attendees"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/fullenrich-event-attendees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.01400 |
| Opus 5 | $0.00000 | $0.00700 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
fullenrich-event-attendees 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 13d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FullEnrich Event Attendees
Turn a list of LinkedIn event attendees into an SDR-ready CSV with verified work emails and mobile phones, using the FullEnrich 20-vendor waterfall.
When This Skill Applies
- "enrich attendees of this event {URL}"
- "enrich this attendees CSV"
- "scrape and enrich LinkedIn event {URL}"
- "FullEnrich event attendees"
Two input modes
The skill does NOT bundle a LinkedIn event scraper. LinkedIn doesn't expose event attendees through any clean public API and Unipile's surface area doesn't cover events either. So the skill ships with two input paths and the user picks:
Mode A — CSV file (recommended). Bring an attendees CSV from any source:
- Manual copy-paste from the LinkedIn event page
- PhantomBuster "LinkedIn Event Attendees Export" automation
- Evaboot Sales Navigator export filtered to event registrants
- Any other tool
Mode B — Apify actor (BYO). The user configures an Apify actor (e.g. giovannibiancia/linkedin-events-partecipants-scraper) under their own Apify account, supplies their LinkedIn cookies via env vars, and the skill runs it. The skill does not pin a specific actor — the user picks one and provides the actor input shape via --actor-input if its keys differ from the defaults.
What This Skill Does NOT Do
- Does not include a built-in LinkedIn event scraper. Pick mode A or B above.
- Does not write outreach copy. Pair with
personalize-messageafter. - Does not push to a CRM.
- Does not spend FullEnrich credits without explicit user approval. See "Credit safety contract" below.
Credit safety contract (MANDATORY)
This skill spends FullEnrich credits, which cost real money. Safeguards:
- Always shows current balance before doing anything.
- Always shows estimated cost of the run.
--max-credits Nceiling (default 500) — auto-trims the contact list to fit.- Hard-approval prompt — blocks on stdin until the user types
yes. Non-TTY without--yesaborts. --dry-runmode — parses input + computes cost preview without spending a credit.
What ships with it
8 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.
- 13d ago First seen · 116 lines · 0 tokens per session scan A 8a75674c5891
fullenrich-event-attendees is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,400 tokens. 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-30.
Other skills, from other repositories
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
kn-spec
Use when creating a specification document for a feature (SDD workflow).
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
kn-flow
Use when orchestrating a full Knowns spec or task wave through planning, implementation, review, integration, and verification, optionally using sub-agents when scopes are parallel-safe.
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.