Borrowing it
Nothing to install: this file belongs to mdcms-ai/mdcms. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mdcms-ai/mdcms/main/AGENTS.mdgit 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/instructions/mdcms-ai/mdcms/agents-md)<a href="https://agentmods.dev/instructions/mdcms-ai/mdcms/agents-md"><img src="https://agentmods.dev/badge/instructions/mdcms-ai/mdcms/agents-md/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/instructions/mdcms-ai/mdcms/agents-md"><img src="https://agentmods.dev/badge/instructions/mdcms-ai/mdcms/agents-md.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.03337 | $0.03337 |
| Opus 5.5 | $0.01335 | $0.01335 |
| Sonnet 5.5 | $0.00667 | $0.00667 |
| Haiku 4.5 | $0.00334 | $0.00334 |
Grade A, and why
mdcms AGENTS.md 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 2mo 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MDCMS
Vision
MDCMS is a Markdown-first headless CMS where the database holds the content but developers work with local files. You pull content down, edit with whatever tools you like, and push it back. The editing experience feels like a filesystem, without the problems that come with actually storing content in one.
Three interfaces share the same data layer: a CLI for developers, an embeddable Studio for editors, and a REST API that AI agents and applications consume directly. The goal is that nobody blocks anyone else. An editor publishing a page and an agent rewriting 500 posts at once go through the same validation, the same permissions, and the same version history.
Direction
The module system is how MDCMS gets extended. Server actions, CLI commands, and Studio UI surfaces all hook in through the same module contract. Community contributions should follow this pattern rather than patching core code.
Upcoming work is focused on live preview (real-time content rendering in the consumer frontend), MCP integration (Model Context Protocol for agent-driven content operations), multiple spaces (team-scoped content organization), and real-time collaboration (multi-user editing via CRDTs).
Repository layout
| Path | What it is |
|---|---|
apps/server |
Elysia HTTP server, the backend for everything |
apps/cli |
CLI binary (mdcms) for push/pull/sync workflows |
apps/studio-example |
Next.js app that embeds the Studio component |
apps/studio-review |
Internal contract-consumer for preview mocks; kept in sync with contracts |
packages/shared |
Contracts, types, and schema utilities used everywhere |
packages/sdk |
Client SDK for reading content from applications |
packages/studio |
The embeddable React Studio component |
packages/modules |
First-party module registry |
skills/ |
Public MDCMS skills pack (skills.sh-distributable) for users adopting MDCMS in their projects |
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.
- 2mo ago First seen · 241 lines · 3,337 tokens per session scan A fbb6708ddcdb
mdcms AGENTS.md is an instructions file published in the GitHub repository mdcms-ai/mdcms (22 stars, last pushed yesterday), licensed MIT. It adds 3,337 tokens to every session, about $0.0133 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.