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 skills add adaptocms/adapto-cms-agent-skills --skill adapto-scaffoldgit clone --depth 1 https://github.com/adaptocms/adapto-cms-agent-skillsWrote 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/adaptocms/adapto-cms-agent-skills/adapto-scaffold)<a href="https://agentmods.dev/skills/adaptocms/adapto-cms-agent-skills/adapto-scaffold"><img src="https://agentmods.dev/badge/skills/adaptocms/adapto-cms-agent-skills/adapto-scaffold/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.
<a href="https://agentmods.dev/skills/adaptocms/adapto-cms-agent-skills/adapto-scaffold"><img src="https://agentmods.dev/badge/skills/adaptocms/adapto-cms-agent-skills/adapto-scaffold.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00076 | $0.02953 |
| Opus 5 | $0.00038 | $0.01477 |
| Sonnet 5 | $0.00015 | $0.00591 |
| Haiku 4.5 | $0.00008 | $0.00295 |
Grade A, and why
adapto-scaffold 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 10d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
adapto:scaffold
The new-project flow. It wraps npx create-adapto-app to stand up a fresh framework app already wired
for Adapto. The read-client ships with create-adapto-app, so this skill doesn't add, vendor, or
maintain any client of its own.
When to use
- Starting a brand-new site/app on Adapto: "create a new adapto project", "scaffold an adapto site", "new adapto app with Next/Astro/SvelteKit".
- Routed here by
adapto:installwhen the target is a new project.
When not to use
- Adding Adapto to an existing repo — out of scope in this variation (
create-adapto-appis for new projects). - Just checking whether the environment is ready →
adapto:doctor.
Inputs
- Project name / target directory — ask; if the user has no preference, default to
my-project(or a short random name). - Framework:
next|astro|sveltekit. - Package manager (optional):
npm|pnpm|yarn|bun. - API key (optional) — prefer not passing it on the command line (see Forbidden actions); set it in
.envafter scaffolding instead.
Outputs
- A new project directory scaffolded for the chosen framework, including Adapto's read-client and a
.env(ADAPTO_API_URL+ADAPTO_API_KEYto fill in). - The
.adapto/studio workspace initialized in the project (empty brain dir, empty ledger,.adapto/.gitignore) — the agent's local source of truth (studio.md). - A clear next step: set the API key in
.env, runnpm run dev, thenadapto:project-defineto build the project brain. (Verify readiness withadapto:doctor.)
Preconditions
- Node.js 20+ and network access —
create-adapto-appruns vianpxand installs dependencies. - Does not require the
adaptoCLI or auth at scaffold time; those are used by later skills (adapto:project-define, content skills, …). The read-client comes fromcreate-adapto-app, not from this repo's templates.
Flow (consent-gated)
Preflight first: run the adapto:doctor checks to learn the toolchain state. Scaffolding
the files needs only Node 20+, so proceed even if auth/tenant aren't set yet (the API-key step is gated on
auth — step 4). If Node < 20, stop. If the adapto CLI is missing/old, flag it (it's needed after scaffolding)
and offer adapto:install — don't silently skip it.
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.
- 10d ago First seen · 153 lines · 76 tokens per session scan A b04f8267495e
adapto-scaffold is a skill published in the GitHub repository adaptocms/adapto-cms-agent-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 2,953 once invoked, about $0.0004 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
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
performance
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
shiny-bslib-theming
Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bstheme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass/CSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection…
shiny-bslib
Build modern Shiny dashboards and applications using bslib (Bootstrap 5). Use when creating new Shiny apps, modernizing legacy apps (fluidPage, fluidRow/column, tabsetPanel, wellPanel, shinythemes), or working with bslib page layouts, grid systems, cards, value boxes, navigation, sidebars, filling layouts, theming…
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.