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 swyxio/skills --skill accelevents-apigit clone --depth 1 https://github.com/swyxio/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/swyxio/skills/accelevents-api)<a href="https://agentmods.dev/skills/swyxio/skills/accelevents-api"><img src="https://agentmods.dev/badge/skills/swyxio/skills/accelevents-api/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/swyxio/skills/accelevents-api"><img src="https://agentmods.dev/badge/skills/swyxio/skills/accelevents-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 10 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00041 | $0.00818 |
| Opus 5 | $0.00020 | $0.00409 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
accelevents-api 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 9d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accelevents API — Speaker Management
API Endpoints
- Base URL:
https://api.accelevents.com/rest/host/event/{eventUrl}/speaker - Event URL for Europe:
ai-engineer-europe-2026 - API Key: stored as
ACCELEVENTS_API_KEYsecret
Authentication
- Read (GET): Use
Authorization: Bearer {key}header - Write (PUT): Use
Key: {key}header — theAuthorization: Bearerheader returns 401 on write operations. This is an undocumented quirk.
GET speakers list
GET /rest/host/event/{eventUrl}/speaker?page=0&size=500
Headers: Authorization: Bearer {api_key}
Returns {"data": [...], "recordsTotal": N}. Each speaker has fields: speakerId, firstName, lastName, email, company, linkedIn, twitter, instagram, bio, title, imageUrl, allowEditSessions, allowOverrideDetails, etc.
PUT (update) speaker
PUT /rest/host/event/{eventUrl}/speaker/{speakerId}
Headers: Key: {api_key}, Content-Type: application/json
Body: { full speaker DTO }
CRITICAL: The PUT endpoint replaces the entire speaker record. Any fields omitted from the request body will be reset to null/false. You MUST:
- Fetch the current speaker data first (via GET)
- Merge your updates into the complete existing data
- Send the full merged payload in the PUT request
Required fields: speakerId, firstName, lastName, email
Fields to always preserve if they exist: company, linkedIn, twitter, instagram, bio, title, pronouns, imageUrl, allowEditSessions, allowOverrideDetails, allowAttendeeAccess, moderator, showModerator, position
Successful response: {"type": "Success", "message": "Speaker updated"}
Bidirectional Sync Workflow
The sync script (src/pages/europe/source/_scripts/sync_accelevents.py) pulls data FROM Accelevents. But schedule.json may have richer data (from prior scraping) that Accelevents lacks. The correct workflow is:
- Pull latest data from Accelevents API
- Compare schedule.json vs API data to find gaps in both directions
- Push UP any data that schedule.json has but Accelevents doesn't (LinkedIn, Twitter, company)
- Pull DOWN any data that Accelevents has but schedule.json doesn't
- Save snapshot after all updates
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.
- 9d ago First seen · 69 lines · 41 tokens per session scan A 161922b7c1b3
accelevents-api is a skill published in the GitHub repository swyxio/skills (158 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 818 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.