Agent skills from Diagrammo — portable SKILL.md files plus a Claude Code and Codex plugin marketplace.
In Claude Code:
/plugin marketplace add diagrammo/skills
/plugin install diagrammo@diagrammo
The plugin brings the skills below, the dgmo MCP server (started with npx -y @diagrammo/dgmo-mcp@<version>, pinned in .mcp.json,
so Node 20 or later is the only prerequisite), and the /diagrammo:diagram-this-repo command, which
runs dgmo-repo-diagrams on the repo you are in.
In Codex (dgmo install codex runs the same two commands):
codex plugin marketplace add diagrammo/skills
codex plugin add diagrammo@diagrammo
Update it with codex plugin marketplace upgrade diagrammo, then start a new Codex session. The Codex plugin has no API key setting: the cloud space tools need DGMO_API_KEY in the server's environment.
Any other agent that reads SKILL.md folders: copy the folder you want from skills/ into that
agent's skills directory.
Reports the codebase report skill made from public repositories: https://diagrammo.github.io/skills/
| Skill | Status |
|---|---|
dgmo-repo-diagrams |
Diagrams of your repo — architecture, key code paths, data model, or the ones you pick from its proposals — checked, with share links |
dgmo-diagramming |
The DGMO language — syntax, chart types, and the MCP tools to check, render and share a diagram. A copy of SKILL.md from diagrammo/dgmo, which generates it |
dgmo-codebase-report |
An onboarding report of your repo — 10 to 15 diagrams from its measured sizes, languages, history and imports, plus what the code shows, built into one report.html |
- Install:
npxdownloads@diagrammo/dgmo-mcpat the version pinned in.mcp.json(Codex:mcp.json) from the npm registry. - The MCP server runs on your machine and checks and renders diagrams locally.
- Cloud space tools: only if you set the plugin's optional Diagrammo space API key setting, which Claude Code keeps in your system's secure credential store. The server then sends that key, and the diagrams you ask it to read or write, to
api.diagrammo.app. With the setting empty, the server makes no network requests. - Share links: the share tool compresses the diagram's source into a link to
online.diagrammo.app. Nothing is uploaded when the link is made. Whoever opens the link sends the diagram, in the URL, to that site, which draws it in their browser and does not store it. The privacy policy covers that site. - Open in app: if the Diagrammo desktop app is installed, the server can open a diagram in it.
- Skill scripts read the repo you run them in and write their output inside it. They send nothing, and they keep the space API key out of the
dgmocommand they run. - Codebase report publishing: only when you say yes at the end of a run. A Cloud space sends each diagram's source to
api.diagrammo.appafter you sign in. The sign-in session, labelled with your machine's host name, is not saved to your machine and shows under Your sessions on the Diagrammo account page until you revoke it; GitHub Pages pushesreport.htmlto agh-pagesbranch of your repo, where it is public. - No personal data, credentials or telemetry.
skills/<name>/SKILL.md one folder per skill, agent-agnostic; scripts it bundles live beside it
.claude-plugin/marketplace.json the Claude Code marketplace; its one plugin is this repo's root
.claude-plugin/plugin.json that plugin's manifest; raise `version` with every release
.mcp.json the plugin's MCP server: dgmo-mcp from npm
.codex-plugin/plugin.json the Codex manifest; same name and version as the Claude one
mcp.json the Codex MCP file (Agent Plugins format); same pin as .mcp.json
.agents/plugins/marketplace.json the Codex marketplace
commands/<name>.md the plugin's slash commands, run as /diagrammo:<name>
docs/ the GitHub Pages showcase; docs/showcase.json lists its reports, scripts/build-showcase.mjs writes its index
tests/ vitest suite; tests/fixtures/repos/ holds small repos to run skills against
pnpm install # also arms the pre-push gate (core.hooksPath .githooks)
pnpm typecheck
pnpm test
MIT