An integration procedure for adding Mantle 0.2 to an existing application or rebuilding an application on it while moving its data. Mantle is a service framework that can add selected data and screens without replacing the application's users, routes, or frontend.

Use it to inspect an application's entry point, sign-in, database, deployment, jobs, and tests; embed Mantle; move bounded data such as forms or catalogs; or rebuild and migrate when appropriate.

It helps decide what Mantle should own before changing a running application, reducing the risk of conflicting data writers or an unnecessary full migration. It also provides a staged path for moving one capability at a time.

integrate — Skill for Claude Code by aotter/mantle

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 aotter/mantle --skill integrate

Clone the repo

git clone --depth 1 https://github.com/aotter/mantle

Made for: Claude Code.

Or install mantle, the plugin that ships this one along with the rest of its 7 skills, 1 MCP server.

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/aotter/mantle/integrate/github.svg)](https://agentmods.dev/skills/aotter/mantle/integrate)

Your own site

<a href="https://agentmods.dev/skills/aotter/mantle/integrate"><img src="https://agentmods.dev/badge/skills/aotter/mantle/integrate/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/aotter/mantle/integrate"><img src="https://agentmods.dev/badge/skills/aotter/mantle/integrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 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.00044	$0.01123
Opus 5.5	$0.00018	$0.00449
Sonnet 5.5	$0.00009	$0.00225
Haiku 4.5	$0.00004	$0.00112

Measured yesterday against content hash bbf2309fcf84, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

docs/skills/integrate/SKILL.md · 97 lines

How it starts

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

Integrate Mantle into an existing application

Mantle is added to a running service; it does not replace it. The service keeps its entry, users, auth, tables, routes and frontend. Mantle adds its own _mantle_* tables, the Schemas it declares, and the surfaces the service chooses to mount. Read the installed package's docs/handbook/start/overview.md and docs/handbook/concepts/authorization.md first.

Inspect and decide

Map the application before installing anything: its entry and router, frontend, users and sign-in, database and data volume, deployment, background jobs and tests. Ask which behavior the owner wants Mantle to own. Then choose:

Embed. Keep the application's entry. Compose Mantle into its existing fetch (createMantle(service, { plan, storage }), the surfaces you want, behind a CallerResolver over the application's own sessions). Best when the application already runs on Workers with D1.
Move one capability at a time. Give one bounded set of data (a form, a catalog) a Schema, then its Views and Procedures; the rest stays. At every step, each table has exactly one writer.
Rebuild and migrate. Generate a new Mantle service in a separate directory, port the frontend and business rules, and import the data. Best when adapting the old structure costs more than rebuilding.

Explain the choice and its tradeoffs to the owner before changing code.

Identity

The application keeps its users. Pick identity:

custom: write src/identity.ts as a CallerResolver over the existing sessions or tokens. subject is the application's stable user id, namespaced when there are several issuers, never an email. Map existing admin roles to owner / editor / contributor, or leave role null.
mantle: only when the application has no sign-in and wants Better Auth's.
none: a public service with no signed-in callers.

Switching identity later is refused; choose deliberately.

Embedding into an existing entry

Read the full file on GitHub · 97 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.

yesterday First seen · 97 lines · 44 tokens per session scan A bbf2309fcf84

Subscribe to this mod's changes

integrate is a skill published in the GitHub repository aotter/mantle (5 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 1,123 once invoked, about $0.0002 per session on Opus 5.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-10-06.

Backend and APIs Databases agent-native ai-agents cloudflare-d1 mcp mcp-server model-context-protocol

datagate

Every DataGate telecom billing API resource - customers, agreements, invoices, sites, products, and more - plus a local SQLite mirror and offline search. Trigger phrases: datagate invoices, datagate customer lookup, pull this month's datagate invoices, use datagate, run datagate.

Servosity/msp-skills · 65 tokens

api-mirror

Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.

cyanheads/pubmed-mcp-server · 68 tokens

integrate

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Integrate Mantle into an existing application

Inspect and decide

Identity

Embedding into an existing entry

What this file has done since we first saw it

Other skills, from other repositories

datagate

api-mirror

api-mirror

api-mirror

api-mirror

api-mirror