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 Immersive-commons/ic-skills --skill immersivecommonsgit clone --depth 1 https://github.com/Immersive-commons/ic-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/immersive-commons/ic-skills/immersivecommons)<a href="https://agentmods.dev/skills/immersive-commons/ic-skills/immersivecommons"><img src="https://agentmods.dev/badge/skills/immersive-commons/ic-skills/immersivecommons.svg" alt="Measured on agentmods" 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.00139 | $0.00839 |
| Opus 5 | $0.00069 | $0.00419 |
| Sonnet 5 | $0.00028 | $0.00168 |
| Haiku 4.5 | $0.00014 | $0.00084 |
Grade A, and why
immersivecommons 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 7d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are holding the umbrella skill for Immersive Commons (immersivecommons.com) — Floor 10 of Frontier Tower, San Francisco. This file tells you which sibling skill to load and the plumbing they all share. It contains no workflows of its own.
Install all IC skills
npx skills add immersive-commons/ic-skills
Canonical source: each skill is also served from https://www.immersivecommons.com/skills/<name>/SKILL.md.
Shared plumbing (read once, applies to every IC skill)
- MCP server:
https://www.immersivecommons.com/api/mcp(Streamable HTTP). Full manifest:https://www.immersivecommons.com/.well-known/ai-agent.json. - Auth: per-user Bearer agent tokens (
agt_…), minted ONLY via a human-approved device-code signup (RFC 8628) — an agent cannot self-mint. Scopes are fixed at mint time; to add a scope, mint a new token. - Public (no-token) surface: THE SIGNAL newsletter reads, news, presentations, donations. Everything else returns
{ok:false, error_kind:"no_token"}until a token is supplied. - First calls:
ic_health(dependency probe), thenic_capabilities(tool catalog + what YOUR token can reach).
Route to the right skill
| Human says… | Load |
|---|---|
| "set me up on IC", "mint a token", "install the MCP server" | ic-onboarding |
| "what's coming up at IC", "RSVP me", "submit a recap" | ic-events |
| "subscribe my agent to IC notifications / the event log" | ic-events-stream |
| "what's in the latest SIGNAL", "search the IC newsletter" | ic-signal (public, no token) |
| "borrow / return a PICO headset", "sign the waiver" | ic-headsets |
| "check my IC agent inbox", "reply to that agent" | ic-inbox |
| "put me on the commits leaderboard" | ic-leaderboard |
| "create / join an agent room", "coordinate agents on a task" | ic-rooms |
| "get me a Z.ai / GLM key for Claude Code" | zai-keys |
| "harden my IC token", "add signature enforcement" | ic-signed-agent |
| "send feedback / a bug report to the IC operator" | ic-feedback |
| "submit a highlight to the floor10 wire" | floor10-submit |
| operator: "review pending members", "approve X" | ic-operator-admin |
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.
- 7d ago First seen · 46 lines · 139 tokens per session scan A 768a4ee929f3
immersivecommons is a skill published in the GitHub repository Immersive-commons/ic-skills (0 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 839 once invoked, about $0.0007 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-31.
Other skills, from other repositories
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.
install
Start a new Mantle site locally from a deterministic starter bundle, or orient and continue an existing local or Mantle landing project. Use when the user gives a Mantle repository URL and asks to try or build with it, invokes the Mantle install skill, wants a new Mantle site, or opens an existing generated site.
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.
plugin
Discover, plan, apply, and verify Mantle marketplace plugins through the Core SDK contract. Use when the user wants to add an installable capability without hand-planning provisioning steps.
theme
Apply brand and visual direction in a generated Mantle project using its repo-owned theme and UI contracts.
update
Check a Mantle project for drift against its Core SDK, starter source, or installed plugin lockfiles.