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/provisionnpx skills add aotter/mantle --skill provisiongit clone --depth 1 https://github.com/aotter/mantleWrote 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/aotter/mantle/provision)<a href="https://agentmods.dev/skills/aotter/mantle/provision"><img src="https://agentmods.dev/badge/skills/aotter/mantle/provision.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 | $0.00059 | $0.01413 |
| Opus 5 | $0.00030 | $0.00707 |
| Sonnet 5 | $0.00012 | $0.00283 |
| Haiku 4.5 | $0.00006 | $0.00141 |
Grade A, and why
provision 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 3d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provision a Mantle Project
Local cold start deliberately stops before this skill. Provision only after the user asks to create remote resources or ship production.
Source of Truth
- Read
.mantle/launch-state.json,.mantle/handoff.md,wrangler.toml, and the current git remotes. - Read installed
@aotter/mantle*versions frompackage.json. - Use matching embedded docs under
node_modules/@aotter/mantle/docs/. - Never infer provider authority from launch state. Confirm the active GitHub and Cloudflare accounts before changing them.
Run the local gate first:
pnpm install --frozen-lockfile
pnpm validate
pnpm typecheck
git status --short
Resume From Observed State
Do not branch on how the project was created. Verify these facts and skip completed work:
git remote get-url originconfirms the GitHub repo.- An HTTPS
PUBLIC_ORIGINthat responds confirms the Cloudflare deploy. /admin/sign-inreturning503 setup_incompletemeans auth is not bound. Use the recorded auth intent only to choose hosted or self-hosted setup; live behavior is authoritative.
If there is no remote, confirm the target account, create a private repo,
commit, and push main. If there is no live Worker, confirm the Cloudflare
account, prefer an available connector, or use pnpm exec wrangler login with
the user's agreement, then run pnpm deploy.
Capture the live URL in PUBLIC_ORIGIN and Public site: in AGENTS.md, then
commit and push non-secret changes. Reuse any repo or Worker already created
by landing. Workers Builds is optional after a direct deploy.
When the owner later adopts a custom domain, update PUBLIC_ORIGIN and the
provider's OAuth callback together, then redeploy. Do not patch site_config
directly; boot syncs its canonical origin from PUBLIC_ORIGIN.
Choose Auth
- Self-hosted — free: configure the owner's per-site GitHub OAuth App and Worker secrets using the steps below.
- Mantle hosted auth — paid: use only when the landing handoff records a hosted allocation and client configuration. Mantle Platform operates the identity provider; do not ask the user for a per-site GitHub OAuth App.
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.
- 3d ago First seen · 168 lines · 59 tokens per session scan A cc1e5c9f2695
provision is a skill published in the GitHub repository aotter/mantle (4 stars, last pushed 8d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,413 once invoked, about $0.0003 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
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
discovery-patterns
Configure ServiceNow Discovery — schedules, IP ranges, credential affinities, MID Server assignment, custom probes/sensors, identification rules, and run-status monitoring on discovery tables.
swag
This skill should be used when the user says "add proxy config", "create reverse proxy", "SWAG config", "nginx proxy", "expose service", "proxy configuration", "subdomain config", "subfolder config", "configure SWAG", "list proxy configs", "view proxy config", "edit proxy config", "remove proxy config", "check proxy…
passport-bootstrap
Use when the user installs mnemo-mcp on a fresh machine and wants to restore prior memory state from S3 or Google Drive (Phase 2 passport sync). Triggers on phrases like "set up mnemo on this machine", "restore my memory passport", "import passport", "bootstrap mnemo", or when the user says they got a new laptop / VM…
chainstack
Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status, searching Chainstack docs, contacting the Chainstack team, or interacting with the Chainstack platform API via…
xfuel-route-compute
Inspect XFuel's 6-tier DePIN compute router and preview which GPU provider a task will hit (Theta EdgeCloud → RapidAPI → MCP → Akash → Render → AWS Bedrock), plus check server health and available chains/models. Use when a user asks "which provider will run this?", "is EdgeCloud available?", "what does XFuel route…