An event workflow for finding upcoming Immersive Commons events, registering for them, and submitting a recap afterward. Immersive Commons is a community that runs events such as coding nights.

Listing upcoming events, RSVPing through the event service, and submitting event recaps.

It keeps event discovery, registration, and follow-up in one guided process. It also checks the access token and asks for the email needed for registration.

ic-events — Skill for Claude Code by Immersive-commons

Install

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.

Any agent

npx skills add Immersive-commons/ic-skills --skill ic-events

Clone the repo

git clone --depth 1 https://github.com/Immersive-commons/ic-skills

Made for: Claude Code.

Or install immersivecommons, the plugin that ships this one along with the rest of its 14 skills, 2 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/immersive-commons/ic-skills/ic-events/github.svg)](https://agentmods.dev/skills/immersive-commons/ic-skills/ic-events)

Your own site

<a href="https://agentmods.dev/skills/immersive-commons/ic-skills/ic-events"><img src="https://agentmods.dev/badge/skills/immersive-commons/ic-skills/ic-events/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/immersive-commons/ic-skills/ic-events"><img src="https://agentmods.dev/badge/skills/immersive-commons/ic-skills/ic-events.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 113 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,796 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00113	$0.01796
Opus 5	$0.00056	$0.00898
Sonnet 5	$0.00023	$0.00359
Haiku 4.5	$0.00011	$0.00180

Measured 8d ago against content hash ea988002458d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade C, and why

ic-events scanned grade C with 2 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 8d 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

**Check `stale`.** If `stale: true`, the cron hasn't refreshed in 90+ min — tell the human "the events feed is stale, here's what I have but it may be missing recent additions." Don't refuse to proceed; the data is still

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -H "Authorization: Bearer $FLOOR10_AGENT_TOKEN" \

.claude/skills/ic-events/SKILL.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You help an agent's human find IC events, RSVP them, and after the event, ship a recap. The flow is read-then-write: the upcoming list is anonymous-safe; the RSVP is scoped + rate-limited + queued.

Pre-flight (always)

Token check. Need FLOOR10_AGENT_TOKEN with events:read_upcoming AND events:rsvp scopes. Smoke probe:
```
curl -H "Authorization: Bearer $FLOOR10_AGENT_TOKEN" \
  https://www.immersivecommons.com/api/events/upcoming
```
200 = good. 401 = no token. 403 from /rsvp later means scope or tier issue.
Email check. RSVP requires explicit email on the agent path (the server doesn't infer for agent callers — trust boundary). Ask the human which email Luma should use. Default to whatever they used at IC signup.

The pipeline (always this order)

1. List upcoming events

curl -H "Authorization: Bearer $FLOOR10_AGENT_TOKEN" \
  "https://www.immersivecommons.com/api/events/upcoming?limit=10"

Response shape:

{
  "ok": true,
  "count": 8,
  "total": 8,
  "generated_at": "2026-05-12T15:00:00.000Z",
  "age_min": 14,
  "stale": false,
  "events": [
    {
      "title": "Vibe Coding Night #32 — MCP harness showdown",
      "when": "2026-05-15T19:00:00-07:00",
      "venue": "Frontier Tower, FT9",
      "host": "Ray, Michalis",
      "luma": "https://luma.com/abc1234"
    }
  ]
}

Check stale. If stale: true, the cron hasn't refreshed in 90+ min — tell the human "the events feed is stale, here's what I have but it may be missing recent additions." Don't refuse to proceed; the data is still useful, just dated.

Filter to what the human cares about. Title-match on what they said; if multiple match, list and ask which. If none match, surface the full list and let them pick.

MCP form:

{
  "name": "ic_events_list_upcoming",
  "arguments": { "limit": 10 }
}

2. Confirm the event (optional, recommended)

If you want to show the human details before RSVPing — venue, time, description — use /api/events/get:

Read the full file on GitHub · 141 lines

Files

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.

INSTALL.md 1.2 KB

Changes

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.

8d ago First seen · 141 lines · 113 tokens per session scan C ea988002458d

Subscribe to this mod's changes

ic-events is a skill published in the GitHub repository Immersive-commons/ic-skills (0 stars, last pushed yesterday), licensed MIT. It adds 113 tokens to every session and 1,796 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (tells the agent never to refuse, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning agent-native ai-agents immersive-commons mcp model-context-protocol openapi

develop

Work on any Mantle project using the Core SDK contract. Use for manifest, runtime, content model, handler, adapter, validation, and MCP work after a project already exists.

aotter/mantle · 38 tokens

provision

Ship a local or Mantle landing-generated project to Cloudflare and finish production auth. Use when a Mantle project is ready for GitHub, Cloudflare deployment, self-hosted GitHub OAuth, paid Mantle hosted auth verification, production smoke testing, or operator handoff.

aotter/mantle · 59 tokens

ic-events