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 lossless-group/lossless-agent-skills --skill event-prepgit clone --depth 1 https://github.com/lossless-group/lossless-agent-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/lossless-group/lossless-agent-skills/event-prep)<a href="https://agentmods.dev/skills/lossless-group/lossless-agent-skills/event-prep"><img src="https://agentmods.dev/badge/skills/lossless-group/lossless-agent-skills/event-prep/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/lossless-group/lossless-agent-skills/event-prep"><img src="https://agentmods.dev/badge/skills/lossless-group/lossless-agent-skills/event-prep.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.00246 | $0.04179 |
| Opus 5.5 | $0.00098 | $0.01672 |
| Sonnet 5.5 | $0.00049 | $0.00836 |
| Haiku 4.5 | $0.00025 | $0.00418 |
Grade A, and why
event-prep 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 yesterday.
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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Prep
Status: draft (2026-10-14). Reverse-engineered from three events done informally (OceanX 2026, Cloudflare Connect 2026, Yotta 2026) and being refined against a live run (RAISE Global Summit 2026). Expect changes after that run.
An event is worth the ticket only if you walk in knowing who matters and why, and walk out with every touchpoint on a record. The skill turns a public event page into a ranked, lens-specific plan before the event, and turns badge photos and business cards into CRM records and a recap afterwards.
All of it lives in two places: markdown in the content repo (the readable brain) and the Twenty CRM (the queryable record). The markdown is generated from research and from the CRM. It never replaces the CRM.
1. Intake: four questions before any research
Answer these first. Ask the operator for any that aren't clear from the request.
| Question | Why it matters | Example answers |
|---|---|---|
| Whose lens? | Decides what "relevant" means, which folder, and which Twenty instance | Lossless / the operator; a client (TWF, LFG) |
| What does the lens want from this room? | Becomes the segment columns and the priority key | TWF: LP capital, deal flow, government mandates. LFG: platform channel partners |
| Attending, or observing? | Prep map vs. a recap of an event nobody attended | OceanX: attending, nobody met yet. Deep Tech Week: not attended |
| What's the source list? | The plan is only as good as the list of who's in the room | Public speaker and sponsor pages; attendee app export; agenda; a list the operator received by email |
Whether there's a list decides how much you can trust the result. With only a public speaker page, everything about who will actually be there is unverified and must say so. Gated attendee lists (Cvent, Swapcard, Brella) are better. Ask for an export before reaching for web research.
2. Routing by lens
| Lens | Series note | Instance prep / map | CRM instance |
|---|---|---|---|
| Operator (Lossless) | content/sources/Events/<Series>.md |
content/sources/Events/<Series> <Year>.md |
Lossless Twenty |
| Client with its own Twenty (TWF, Palmer AI) | content/sources/Events/<Series>.md |
see open question below | that client's Twenty |
| Client without a Twenty (LFG) | content/sources/Events/<Series>.md |
content/client-content/<Client>/Events/<Event>-<Year>.md |
Lossless Twenty, if anything |
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.
- yesterday First seen · 281 lines · 246 tokens per session scan A cc47a1960f94
event-prep is a skill published in the GitHub repository lossless-group/lossless-agent-skills (4 stars, last pushed 2d ago), licensed MIT. It adds 246 tokens to every session and 4,179 once invoked, about $0.0010 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-10-15.
Other skills, from other repositories
code-sync
Reconcile the project's documents with what the code now shows, after a merge or at the end of a build: spec statuses (building → done only with a named gate, or → stale with the reason), assumed specs owed ratification, the project README map and its Last verified date. Surgical edits only. Use when the user says…
status
Show what structured context exists and what's missing. Overview of bundles, SCDs, coverage across all 11 concepts, and compilation sync status.
gsd-new-project
Initialize a new project with deep context gathering and PROJECT.md.
gsd-ns-manage
config workspace | workstreams thread update ship inbox.
utility-pm-skill-iterate
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…