develop

A development guide for existing Mantle projects that use the Mantle Core SDK. It covers project manifests, runtime behavior, content models, handlers, adapters, validation, and MCP integrations.

In plain words
What is it for?
Use it to modify an existing Mantle site’s configuration, runtime, content, authentication, adapters, validation, or MCP features.
Why use it?
It keeps changes aligned with the installed Mantle version and the project’s active configuration. It also points to the local Core documentation and matching examples before new patterns are created.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/aotter/mantle/develop
Any agent
npx skills add aotter/mantle --skill develop
Clone the repo
git clone --depth 1 https://github.com/aotter/mantle

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,296 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.02296
Opus 5 $0.00019 $0.01148
Sonnet 5 $0.00008 $0.00459
Haiku 4.5 $0.00004 $0.00230

Measured yesterday against content hash 6ea1ef2c947f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

develop scanned grade A with 1 finding 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.

Makes network callslowCapability

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

curl -i http://localhost:8787/mcp
skills/develop/SKILL.md · 228 lines

How it starts

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

Mantle Develop

This is the Core workflow skill for an existing Mantle project. Repo-local copies are byte-for-byte projections from the installed package; its embedded docs govern runtime/API behavior.

First Read

  1. package.json for the installed @aotter/mantle* versions.
  2. manifests/site.yaml, the active adapter config, and src/auth.ts when present. If the project is older, check src/mantleConfig.ts.
  3. The active .mantle/overlays/<type>/seed.json, when present; generated homepages commonly import visible copy and form structure from it.
  4. Optional local context: .mantle/launch-state.json, .mantle/handoff.md, .mantle/plugins.json, .mantle/plugins.lock.json, and .mantle/recipes/.
  5. Installed Core docs in node_modules/@aotter/mantle/docs/.

If node_modules/ is missing, run pnpm install --frozen-lockfile before falling back to remote docs. Remote docs must use a tag matching the installed version; never use develop branch docs for a versioned consumer project.

Existing Examples

Before inventing a Mantle pattern, inspect aotter/mantle-starters. Use a tag matching the installed Mantle version when available; use develop only for unreleased work. blank/ shows the base application shape and overlays/<type>/ contains working examples of manifests, handlers, routes, page seeds, and feature wiring. Copy the smallest matching pattern. Do not edit or copy generated provision-bundles/*.json by hand.

Public rendering is opt-in consumer wiring: mountPublicRoutes, a TemplateRegistry, and a matching publicPathResolver must agree on the exposed collections. Do not auto-publish every Schema. Generated projects list their mounted URL surface in their own README. Import the registry and resolver from @aotter/mantle/web; Core runtime does not install public rendering by itself.

Authoring CLI

Use the project's scripts first; generated projects expose the shipping mantle authoring CLI from @aotter/mantle. Ask the installed CLI for its command list instead of trusting one copied into prose — the surface is version-matched and changes between releases:

Read the full file on GitHub · 228 lines

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.

  1. yesterday First seen · 228 lines · 38 tokens per session scan A 6ea1ef2c947f

Subscribe to this mod's changes

develop 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 2,296 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

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…

Immersive-commons/ic-skills · 161 tokens

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…

Immersive-commons/ic-skills · 133 tokens

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…

Immersive-commons/ic-skills · 189 tokens

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…

Immersive-commons/ic-skills · 112 tokens

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…

Immersive-commons/ic-skills · 124 tokens

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"…

Immersive-commons/ic-skills · 122 tokens