Borrowing it
Nothing to install: this file belongs to diagrammo/dgmo-mcp. 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/diagrammo/dgmo-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/diagrammo/dgmo-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/instructions/diagrammo/dgmo-mcp/claude-md)<a href="https://agentmods.dev/instructions/diagrammo/dgmo-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/diagrammo/dgmo-mcp/claude-md.svg" alt="Measured on agentmods" 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.03373 | $0.03373 |
| Opus 5 | $0.01687 | $0.01687 |
| Sonnet 5 | $0.00675 | $0.00675 |
| Haiku 4.5 | $0.00337 | $0.00337 |
Grade A, and why
dgmo-mcp CLAUDE.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 8d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dgmo-mcp — @diagrammo/dgmo-mcp
The MCP server that gives Claude Code, Claude Desktop, Cursor and any MCP client the ability to author, validate and render DGMO — over stdio, or over streamable HTTP since 0.19.0. Published to npm as @diagrammo/dgmo-mcp, listed on the MCP registry as io.github.diagrammo/dgmo-mcp, and shipped as a .mcpb bundle on the GitHub release.
Commands
pnpm build # tsup — 4 ESM entries + .d.ts
pnpm test # vitest run
pnpm check:all # deadcode + duplication + deps + test — what CI runs, and the gate before a release
pnpm check:triggers # drift guard: triggers.json vs dgmo-content/registry.json — NOT in check:all, NOT in CI
./preflight.sh # version sync, pack, fresh-install MCP probe. Runs on tag push (.githooks/pre-push). Runs NO tests
pnpm studio # guidance studio (the README's `pnpm hub` / `pnpm harness` scripts do not exist)
✅ The repo is prettier-clean, and check:all now enforces it — format:check runs first in the gate as of 2026-08-06, so pnpm format is safe to run bare and drift cannot accumulate again. It had: 47 files under tools/, tests/ and src/ were failing, and because nothing checked, one pnpm format during unrelated work turned an 8-file change into a 55-file one. If check:all fails on formatting, run pnpm format and commit that alone — never as a rider on a feature.
Depending on dgmo
It consumes the published @diagrammo/dgmo from npm, never the workspace checkout — there is no symlink here, unlike the app. Workspace dgmo edits are invisible until dgmo is published and the dep bumped, or until pnpm link ../dgmo (see CONTRIBUTING.md; pnpm install undoes it).
🔴 Since 2026-08-07 the library is a devDependency and is INLINED into the bundle (noExternal in tsup.config.ts), exactly as @diagrammo/dgmo-cli does it. Declaring it at runtime meant every install of this server — and every npm i -g @diagrammo/dgmo-cli, which spawns it — unpacked the library plus its d3, dagre and lz-string trees: 17,028 KB, on top of a CLI bundle that already inlines the same library and never loads that copy. A CLI install measured 73,956 KB before and 63,344 KB after.
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.
- 8d ago First seen · 70 lines · 3,373 tokens per session scan A 56de33cd5c0a
dgmo-mcp CLAUDE.md is an instructions file published in the GitHub repository diagrammo/dgmo-mcp (3 stars, last pushed 3d ago), licensed MIT. It adds 3,373 tokens to every session, about $0.0169 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 instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.