mdcms-studio-embed

mdcms-studio-embed is a skill for Claude Code, Codex from mdcms-ai/mdcms. It costs 114 tokens per session (1,777 once invoked), scanned A, original, MIT.

A workflow for placing the MDCMS Studio editing interface inside a React application, such as a Next.js site. Editors can use the content-management interface under a route in the host app, such as /admin.

In plain words
What is it for?
Use it to add an embedded Studio route to a React, Next.js, or Remix application and connect it to an MDCMS server.
Why use it?
It avoids making editors switch to a separate site and explains the app route, package setup, and server access configuration needed for embedding.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add an embedded Studio route to a React, Next.js, or Remix application and connect it to an MDCMS server.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mdcms-ai/mdcms/mdcms-studio-embed
Install

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.

Any agent
npx skills add mdcms-ai/mdcms --skill mdcms-studio-embed
Clone the repo
git clone --depth 1 https://github.com/mdcms-ai/mdcms

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mdcms-studio-embed

README.md
[![agentmods](https://agentmods.dev/badge/skills/mdcms-ai/mdcms/mdcms-studio-embed/github.svg)](https://agentmods.dev/skills/mdcms-ai/mdcms/mdcms-studio-embed)
Your own site
<a href="https://agentmods.dev/skills/mdcms-ai/mdcms/mdcms-studio-embed"><img src="https://agentmods.dev/badge/skills/mdcms-ai/mdcms/mdcms-studio-embed/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.

agentmods 80×15 button for mdcms-studio-embed

Your own site · 80×15
<a href="https://agentmods.dev/skills/mdcms-ai/mdcms/mdcms-studio-embed"><img src="https://agentmods.dev/badge/skills/mdcms-ai/mdcms/mdcms-studio-embed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 114 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00114 $0.01777
Opus 5.5 $0.00046 $0.00711
Sonnet 5.5 $0.00023 $0.00355
Haiku 4.5 $0.00011 $0.00178

Measured 1mo ago against content hash 6bdaa93380dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mdcms-studio-embed 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.

skills/mdcms-studio-embed/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

MDCMS Studio Embed

Mount the MDCMS Studio UI inside the user's own host app so editors work alongside product code. The canonical reference is apps/studio-example in the MDCMS repo — use it as the copy-from template for route structure, config preparation, and client bootstrap.

When to use this skill

The user wants a Studio UI under their own domain (e.g. app.example.com/admin/...) instead of running Studio standalone. If they only need the API and use Studio at the server's own /admin/studio route, skip.

Prerequisites

  • A reachable MDCMS server and a working mdcms.config.ts (run mdcms-brownfield-init or mdcms-greenfield-init first).
  • A React app, ideally Next.js App Router. Other frameworks work but the reference implementation is Next.
  • Ability to set server-side env vars on the MDCMS backend (for MDCMS_STUDIO_ALLOWED_ORIGINS).

Steps

1. Install the Studio package in the host app

npm install @mdcms/studio
# or: bun add @mdcms/studio

2. Add a catch-all route

Studio is a single page app embedded at a catch-all route. The reference uses /admin/[[...path]] so every Studio route is served from one Next page. Copy the pattern from apps/studio-example/app/admin/[[...path]] in the MDCMS repo:

app/
  admin/
    [[...path]]/
      page.tsx        # server component that prepares Studio config
      layout.tsx      # minimal layout (Studio brings its own chrome)
    admin-studio-client.tsx   # client wrapper that mounts <Studio />
    studio-config.ts          # prepareStudioConfig + client-serialized subset

The server component calls prepareStudioConfig from @mdcms/studio/runtime against the full mdcms.config.ts, extracts a client-safe subset (component metadata, schema hash, route metadata), and passes it to the client wrapper.

3. Wire the prepared config to <Studio />

The client wrapper uses the <Studio /> component and the prepared config:

"use client";
import { Studio } from "@mdcms/studio";
import type { MdcmsConfig } from "@mdcms/studio";

export function AdminStudioClient({ config }: { config: MdcmsConfig }) {
  return <Studio config={config} />;
}

Read the full file on GitHub · 131 lines

Changes

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.

  1. 1mo ago First seen · 131 lines · 114 tokens per session scan A 6bdaa93380dd

Subscribe to this mod's changes

mdcms-studio-embed is a skill published in the GitHub repository mdcms-ai/mdcms (22 stars, last pushed 3d ago), licensed MIT. It adds 114 tokens to every session and 1,777 once invoked, about $0.0005 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-30.

Related

Other skills, from other repositories

webiny-api-cms-content-models

Creating Headless CMS content models via code using the ModelFactory pattern. Use this skill when the developer wants to create, modify, or understand content model definitions, define fields and validators, set up reference fields between models, configure field layouts (including nested layouts inside object or…

webiny/webiny-js · 313 tokens

webiny-form-model

Building forms with the FormModel system — field types, renderers, layout, validation, conditional rules, computed fields, and dynamic zones. Use this skill when the developer needs to define form fields with the builder API, choose renderers, build layouts with tabs/rows/separators, add validation (Zod or…

webiny/webiny-js · 93 tokens

webiny-api-architect

The hub skill for all API/backend architecture in Webiny. Covers architecture overview, Services vs UseCases, feature naming and organization, feature structure templates, DI decision tree, anti-patterns, createFeature, createAbstraction, container registration, domain errors, entity patterns, naming conventions…

webiny/webiny-js · 90 tokens

webiny-v5-to-v6-migration

Migration patterns for converting v5 Webiny code to v6 architecture. Use this skill when migrating existing v5 plugins to v6 features, converting context plugins to DI services, adapting v5 event subscriptions to v6 EventHandlers, or understanding how v5 patterns translate to v6. Targeted at AI agents performing…

webiny/webiny-js · 75 tokens

webiny-admin-architect

Admin-side architecture patterns for Webiny extensions. Use this skill when building frontend features with headless features (UseCase/Repository/Gateway), presentation features (Presenter/ViewModel/hooks/components), MobX-based presenters, RegisterFeature, and Admin BuildParams. Covers the admin/ directory structure…

webiny/webiny-js · 71 tokens

webiny-cognito-federation

Configuring Cognito Federation for Webiny projects — federated sign-in via external identity providers (Google, Facebook, Apple, Amazon, OIDC/Entra ID) while keeping Cognito as the user pool. Use this skill when the developer asks about Cognito federation, SSO with Cognito, adding Google/Microsoft/OIDC login to…

webiny/webiny-js · 126 tokens