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-schema-applygit 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-schema-apply)<a href="https://agentmods.dev/skills/adaptocms/adapto-cms-agent-skills/adapto-schema-apply"><img src="https://agentmods.dev/badge/skills/adaptocms/adapto-cms-agent-skills/adapto-schema-apply/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-schema-apply"><img src="https://agentmods.dev/badge/skills/adaptocms/adapto-cms-agent-skills/adapto-schema-apply.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.00064 | $0.02447 |
| Opus 5 | $0.00032 | $0.01223 |
| Sonnet 5 | $0.00013 | $0.00489 |
| Haiku 4.5 | $0.00006 | $0.00245 |
Grade A, and why
adapto-schema-apply 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 9d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
adapto:schema-apply
The gated writer of the schema pair. It reads .adapto/schema-plan.json (produced by
adapto:schema-design) and creates the Article categories and custom collections it describes via
the adapto CLI. It is idempotent and re-runnable — existing collections/categories are reused or
updated, never duplicated.
When to use
- After
adapto:schema-designproduced (and you've eyeballed or hand-edited).adapto/schema-plan.json, and you're ready to create those collections + categories in Adapto. - Triggers: "apply the schema", "create the collections", "build my schema in Adapto".
When not to use
- No plan file yet → run
adapto:schema-designfirst. - Seeding content rows into the collections →
adapto:content-seed.
Inputs
.adapto/schema-plan.json— the approved plan (collections, categories, language). Missing/invalid → stop and route toadapto:schema-design.- The working tenant — confirm it explicitly; never assume the saved/active one. With 2+ tenants, have the user pick; with one, state it and proceed.
Outputs
- The plan's Article categories and custom collections created (or updated) in the CMS,
draftunless the plan says otherwise. - The reserved
_adapto_seocollection ensured (the CMS home for per-piece SEO metadata — reserved-slugs.md), soadapto:content-uploadcan write metadata. - A realized
.adapto/schema.json— a{"<slug>": "<id>", …}map of every collection's slug to its CMS id (incl._adapto_seo) — foradapto:content-upload(andadapto:content-seed) to target. - A report: which collections/categories were created vs reused, with ids.
- Next step: suggest
adapto:content-researchto start a content cycle (research → plan → create → upload), oradapto:content-seedfor a quick set of starter drafts. Both read.adapto/schema.json.
Preconditions
- Preflight with the
adapto:doctorchecks. - Hard-block on an authenticated CLI (
adapto auth me) and a selected tenant — this skill writes. .adapto/schema-plan.jsonmust exist (else route toadapto:schema-design).adaptoCLI>= 0.1.3.
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.
- 9d ago First seen · 145 lines · 64 tokens per session scan A 9a4ea2d7e615
adapto-schema-apply is a skill published in the GitHub repository adaptocms/adapto-cms-agent-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 2,447 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
demographic-modeling
This skill should be used when the user asks to "design a demographic model", "model a person/organisation/role", "design party relationships", "plan identity structures", or "work with demographic archetypes". Covers designing openEHR demographic models using the PARTY hierarchy, roles, capabilities, relationships…
offensive-api-abuse
Advanced API exploitation methodology focused on business logic abuse and sophisticated attack patterns that bypass traditional security controls. Covers business logic bypass through API call chaining and workflow manipulation. Addresses GraphQL-specific attacks including batching for credential brute-force, query…
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
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.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
perf
Analyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto optimization, genserver bottlenecks. Use when slowness, timeouts, or high memory reported.