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/themenpx skills add aotter/mantle --skill themegit 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.00022 | $0.00723 |
| Opus 5 | $0.00011 | $0.00362 |
| Sonnet 5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
theme 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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mantle Theme
Theme work is project-owned source editing. Starters may ship UI files, tokens, or recipes, but the skill contract is Core-owned.
First Read
.mantle/handoff.mdand.mantle/recipes/if present.styles/,components/,src/web/,src/theme*, and UI-library config if present.- A vendored UI palette's manifest and license, if present.
manifests/site.yamlto understand which content shape drives the public UI.
Ownership
styles/globals.cssis the token contract. Start a whole-site reskin with its:rootand.darkvalues; runtime components inherit those variables.components/is the runtime-facing component surface when present.src/web/is project-owned composition; put new sections there.public/site-icon.svgandpublic/site-icon.pngare one site identity. Keep both listed insrc/mantle/config.ts > siteDefaults.icons: PNG first as the 64x64 compatibility rendition, then SVG as the editableanysize source. The same list drives browser favicons, Admin chrome, and MCPserverInfo.icons; do not edit generated files underpublic/_mantle/.- If the project includes a vendored UI reference palette, treat it as
offline source material and provenance, not runtime source. Copy only a
needed primitive or block into the project's runtime directories, or
fork/wrap it under
src/web/sections/; do not import the palette from Worker or runtime code.
Work
- Use existing tokens, CSS, components, and installed dependencies first.
- When replacing the site mark, regenerate PNG from the same SVG artwork so every surface presents the same identity. Check it at the Admin's 28px slot in both light and dark themes; a single high-contrast rendition is preferred over theme-specific variants unless the artwork genuinely needs both.
- For a standard hero image, set the section's
image: { src, alt }; useshowImage: falsefor text-only hero/content blocks. Put non-image media in a project-owned section. - Keep accessibility basics: semantic HTML, focus states, contrast, and
keyboard reachability. Against a non-default background, check
--foreground-mutedand--primary, not only--foreground; keep normal text at 4.5:1 or better. - Do not require registry access for a project that already vendors UI source.
- Add UI dependencies only when existing source cannot cover the requested change.
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.
- 2d ago First seen · 71 lines · 22 tokens per session scan A f36cb533d735
theme is a skill published in the GitHub repository aotter/mantle (4 stars, last pushed 7d ago), licensed Apache-2.0. It adds 22 tokens to every session and 723 once invoked, about $0.0001 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
reskin
Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…
frontend-design-taste
Build distinctive frontends that avoid generic AI aesthetics. Provides anti-slop enforcement, variance dials, art direction archetypes, creative arsenal, and performance guardrails. Use when creating new landing pages, UI components, design systems, or when the user says "make it look good", "design direction", "avoid…
frontend-frontier
Use when the user wants a high-signal frontend, distinctive art direction, strong motion design, 3D/parallax, shader effects, landing pages, docs sites, dashboards, or a tokenized design system that avoids generic AI-generated UI.
ui-conventions
Use when writing or changing any UI in todox — a page, a component, Tailwind classes, or CSS. Covers the helpers to reach for before inventing one, and the layout rules that keep the app usable on a phone.
clean-interface-design
Design clean, calm, uncluttered interfaces that don't read as templated AI output. Use when building or restyling any UI (web, iOS, Android, macOS) and it needs visual hierarchy, restraint, spacing discipline, one clear primary action, and a cohesive look. Covers accent color, whitespace, corner radius, type scale…
motion-and-animation
Add motion and animation that feels great, not like slop. Use when animating any UI — transitions, hovers, presses, sheets, drawers, modals, page transitions, gestures — or when an animation feels "off". Covers the easing rules agents get wrong (ease-out for enter, ease-in for exit), springs, interruptibility…