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 agentmods add skills/aotter/mantle/pluginnpx skills add aotter/mantle --skill plugingit clone --depth 1 https://github.com/aotter/mantleWhat 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 | $0.00038 | $0.00892 |
| Opus 5 | $0.00019 | $0.00446 |
| Sonnet 5 | $0.00008 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
plugin 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mantle Plugin
Mantle plugins are Core SDK capability packages. They are not starter overlays and they are not provider provisioning scripts.
A plugin may contribute:
- manifests:
Schema,View,Procedure,Trigger; - handler source or handler registration notes;
- site defaults or media policy additions;
- expected HTTP, admin, and MCP surfaces;
- adapter capability requirements and provider setup notes.
User Install Entry
The user-facing install path is:
Use repo-local mantle:plugin to install <plugin slug or recipe URL> in this repo.
Use repo-local mantle:plugin to update <plugin id> in this repo.
Use repo-local mantle:plugin to remove <plugin id> from this repo.
There is no mantle plugin add CLI yet. Do not invent one. Install from a
marketplace entry, plugin package, or recipe URL that declares enough data for
an agent to apply the capability deterministically.
A valid marketplace entry must include:
- plugin id, title, source, and version;
- supported Mantle version range;
- files, manifests, handlers, routes, MCP tools, and admin surfaces it adds;
- adapter capabilities and provider resources it requires;
- required env vars and secrets, without secret values;
- verification commands and expected surfaces.
If the marketplace page is only marketing copy or lacks an install recipe, stop and ask for the recipe instead of guessing.
First Read
package.jsonfor Mantle version and adapter package.manifests/site.yamlfor current atom names and route/tool collisions.src/mantle/config.tsandsrc/mantle/handlers/for registered handlers, templates, and optional ports. Older projects may usesrc/mantleConfig.ts..mantle/plugins.jsonand.mantle/plugins.lock.jsonif present..mantle/launch-state.jsononly as context, not as plugin authority.
Plan First
Before applying any plugin, produce a plan:
- files to add or change;
- atoms to add and their names;
- HTTP routes and MCP tools that will appear;
- required runtime ports;
- adapter-specific resources, env vars, and secrets;
- checks to run.
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 · 121 lines · 38 tokens per session scan A 0267b3a6d788
plugin is a skill published in the GitHub repository aotter/mantle (4 stars, last pushed 6d ago), licensed Apache-2.0. It adds 38 tokens to every session and 892 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-31.
Other skills, from other repositories
ic-events-stream
Teach a member's AI agent to subscribe to the Immersive Commons agentic event log and route notifications itself — tier decisions, inbox envelopes, and more as IC adds append sites. IC publishes "things happening for me" events; the agent polls, then decides routing (Telegram / Slack / toast / auto-act / nothing) on…
ic-feedback
Submit feedback, feature requests, praise, complaints, questions, suggestions, or breakage reports to the Immersive Commons operator on a user's behalf. Available to EVERY tier (public through operator) — no token required for the REST path. Use when the user says "I wish IC had X", "the kiosk is broken", "this doc is…
zai-keys
Request and use a Z.ai (GLM) Claude-Code-compatible key from Immersive Commons — a 5-hour walk-in WORKSHOP pass (public tier, tied to an event) or a weekly-token MEMBER key (ic-member, pick a multiplier). Use when the human says "get me a Z.ai key", "I need a GLM key for the workshop", "set up Claude Code on the IC…
ic-leaderboard
Connect a user's GitHub account to the Immersive Commons commits leaderboard, opt them in, and verify their rank. Use when the human says "put me on the leaderboard", "get me on /floor10/commits", "connect my GitHub to IC", "show me my leaderboard rank", or "opt me out of the commits board". Requires an IC agent token…
ic-onboarding
Set an agent's human user up on Immersive Commons end-to-end, explaining every step to them in plain English — mint a token, install + verify the MCP server, set their profile, EDUCATE them on everything IC offers, and file a quality tier-upgrade request. Use when the human says "set me up on IC", "connect me to…
ic-signed-agent
Upgrade an Immersive Commons agent token from bearer-only to bearer + Ed25519 signature (RFC 9421 strict subset). A leaked bearer alone is useless against tokens with signature enforcement on — the agent must also possess the private key. Use when the human says "make my IC agent more secure", "rotate my agent key"…