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 mdcms-ai/mdcms --skill mdcms-brownfield-initgit clone --depth 1 https://github.com/mdcms-ai/mdcmsWrote 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/mdcms-ai/mdcms/mdcms-brownfield-init)<a href="https://agentmods.dev/skills/mdcms-ai/mdcms/mdcms-brownfield-init"><img src="https://agentmods.dev/badge/skills/mdcms-ai/mdcms/mdcms-brownfield-init/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/mdcms-ai/mdcms/mdcms-brownfield-init"><img src="https://agentmods.dev/badge/skills/mdcms-ai/mdcms/mdcms-brownfield-init.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 24 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 55 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 96 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00116 | $0.01824 |
| Opus 5.5 | $0.00046 | $0.00730 |
| Sonnet 5.5 | $0.00023 | $0.00365 |
| Haiku 4.5 | $0.00012 | $0.00182 |
Grade A, and why
mdcms-brownfield-init 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDCMS Brownfield Init
Onboard an existing repository whose content already lives as .md/.mdx files on disk. mdcms init is the one-shot command that creates mdcms.config.ts, infers a schema from the existing files, syncs that schema to the server, and imports the files as draft documents.
When to use this skill
The user has:
- an MDCMS backend reachable (if not, run
mdcms-self-host-setupfirst), and - a repo with Markdown/MDX content they want MDCMS to manage.
Do not use this skill for empty repos — use mdcms-greenfield-init instead.
Prerequisites
- Server URL (e.g.
http://localhost:4000). - An MDCMS API key with permission to create projects/environments and sync schema. Create one via Studio → Settings → API Keys, or use the demo key from
docker-compose.dev.ymlfor local development. - A project slug and environment name (defaults to
productionif omitted). - Node.js / npm — the CLI is
npx mdcms(orbun x mdcms).
Steps
1. Discover the content directories
find . -type f \( -name '*.md' -o -name '*.mdx' \) \
-not -path '*/node_modules/*' -not -path '*/.*' \
| awk -F/ '{print $2"/"$3}' | sort -u
List the top two directory levels (for example content/posts, docs/blog). Confirm with the user which of these MDCMS should manage. Those become --directory values in step 3.
2. Prepare the non-interactive flags
Collect these inputs up front. If any are missing and the user wants headless, stop and ask:
| Flag | Value |
|---|---|
--server-url |
MDCMS API base URL |
--project |
slug to create on the server (e.g. my-site) |
--environment |
environment name (default production) |
--api-key |
token with project create + schema sync scopes |
--directory |
one per managed directory, repeatable |
Alternatively, set the corresponding env vars (MDCMS_SERVER_URL, MDCMS_PROJECT, MDCMS_ENVIRONMENT, MDCMS_API_KEY) and omit the flags.
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 · 129 lines · 116 tokens per session scan A e231465dd6c5
mdcms-brownfield-init is a skill published in the GitHub repository mdcms-ai/mdcms (22 stars, last pushed 3d ago), licensed MIT. It adds 116 tokens to every session and 1,824 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.
Other skills, from other repositories
review
Review one pull request for real bugs, regressions, and convention violations. Enumerate candidate issues across the whole diff, verify each against the code, then return structured line-anchored findings and a verdict. Read-only on GitHub; the orchestrator posts the review.
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.
emdash-cli
Use the EmDash CLI to inspect and manage an EmDash instance from the command line, including content, schema, media, taxonomies, menus, search, authentication, seeds, migrations, generated types, and whole-site export and import.
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…
building-emdash-site
Build the site-facing parts of an EmDash CMS project on Astro, including schema and seeds, content queries, Portable Text rendering, menus, taxonomies, widgets, and deployment configuration. Use for EmDash site and theme work; use creating-plugins instead when the task is plugin authoring alone.
agent-browser
Use the agent-browser CLI to exercise web interfaces, inspect rendered accessibility state, verify interactions, and capture screenshots. Use for browser-based UI testing and evidence collection. Do not use as a substitute for deterministic Playwright coverage when an automated regression test is the requested…