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 instantcms-dev/instantcms-mcp --skill instantcms-addongit clone --depth 1 https://github.com/instantcms-dev/instantcms-mcpWrote 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/instantcms-dev/instantcms-mcp/instantcms-addon)<a href="https://agentmods.dev/skills/instantcms-dev/instantcms-mcp/instantcms-addon"><img src="https://agentmods.dev/badge/skills/instantcms-dev/instantcms-mcp/instantcms-addon/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/instantcms-dev/instantcms-mcp/instantcms-addon"><img src="https://agentmods.dev/badge/skills/instantcms-dev/instantcms-mcp/instantcms-addon.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.00031 | $0.00168 |
| Opus 5.5 | $0.00012 | $0.00067 |
| Sonnet 5.5 | $0.00006 | $0.00034 |
| Haiku 4.5 | $0.00003 | $0.00017 |
Grade A, and why
instantcms-addon 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 1mo 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.
What it actually says
InstantCMS addon
Use the project's MCP tools as the primary source for structures, hooks, and component APIs.
Before generation, determine the smallest addon type that satisfies the request. Look up every referenced hook and unfamiliar component API; do not invent framework methods.
After generation, run validate_addon, inspect every error diagnostic, and perform the repository checks described in AGENTS.md. Do not call an addon ready while validation errors remain.
Read references/backend.md when the addon has administration UI. Read references/packaging.md only when producing an installable archive or release tree.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 15 lines · 31 tokens per session scan A be45203c7296
instantcms-addon is a skill published in the GitHub repository instantcms-dev/instantcms-mcp (11 stars, last pushed 9d ago), licensed MIT. It adds 31 tokens to every session and 168 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
payload
Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
creating-plugins
Create EmDash CMS plugins with sandboxed hooks, routes, storage, content and media APIs, MCP tools, and declarative admin UI, or native React and Astro extensions. Use when scaffolding or implementing an EmDash plugin.
writing-emdash-docs
Write, revise, and review EmDash documentation for technical accuracy, useful structure, house style, and natural prose. Use when working on user documentation, guides, API reference pages, migration or upgrade guides, READMEs, contributor documentation, technical specifications, or release notes in the EmDash…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
build-fullstack-backend
ONLY for writing backend or fullstack code BY HAND. NOT needed on the normal path — createartifact(fullstack-stateless-app or fullstack-stateful-app) followed by generateartifact writes the backend, verifies it by importing it and launches it. Recall this when editing an existing fullstack artifact, or when…
api-design
Use this skill when designing, implementing, or reviewing an HTTP API — endpoints, request and response shapes, errors, pagination, versioning, and authorization. Triggers: user says "API", "endpoint", "REST", "route", "status code", "pagination", "request body", "response shape", "OpenAPI", "versioning"…