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 agentmods add instructions/miroapp/miro-ai/claude-mdgit clone --depth 1 https://github.com/miroapp/miro-aiWrote 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/miroapp/miro-ai/claude-md)<a href="https://agentmods.dev/instructions/miroapp/miro-ai/claude-md"><img src="https://agentmods.dev/badge/instructions/miroapp/miro-ai/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.00568 | $0.00568 |
| Opus 5 | $0.00284 | $0.00284 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
miro-ai 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Miro AI Developer Tools - A plugin/integration repository connecting AI coding assistants (Claude Code, Gemini CLI, Kiro, and other MCP clients) to Miro boards. This is primarily a documentation and configuration repository - not a traditional compiled codebase.
CRITICAL
- NO code without vendor documentation check first.
- Make sure you understand how Claude Code plugins work by reading the relevant MCP documentation.
- Reduce the level of verbosity in your response to be concise and to the point.
- You must provide clear, direct answers and avoid unnecessary explanations or elaborations.
- Use diagrams, tables, or bullet points to explain.
- Provide working code and references to it instead of code snippets.
- Keep architecture implementation simple, concise, performant, and modular.
- Use conventional commits
Repository Structure
miro-ai/
├── .agents/
│ └── skills/ # Repo-local helper skills for agent workflows
├── claude-plugins/ # Claude Code plugins
│ └── miro/ # Core MCP integration with bundled skills (browse, code-review, code-spec, code-explain-on-board, diagram, doc, table)
├── codex-plugins/ # Codex plugins (auto-generated)
├── copilot-cowork-plugins/ # GitHub Copilot Cowork packages (auto-generated)
├── cursor-plugins/ # Cursor plugins (auto-generated)
├── gemini-extension.json # Gemini CLI extension manifest at repo root (auto-generated)
├── skills/ # Agent Skills mirror (auto-generated, also serves as Gemini extension's bundled skills)
├── powers/ # Kiro powers
│ └── code-gen/ # Design-to-code (POWER.md + mcp.json)
├── validation/ # Validators, converters, installers
│ ├── schemas/ # JSON schemas for frontmatter
│ └── src/ # TypeScript drivers
│ ├── converters/ # bun run convert
│ └── installer/ # bun run plugins:install:*
├── docs/ # Documentation
├── .claude-plugin/ # Marketplace manifest
├── gemini-extension.json # Gemini CLI extension
├── package.json # Bun project config
└── CONTRIBUTING.md
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.
- 5d ago First seen · 53 lines · 568 tokens per session scan A e9943b3d3afe
miro-ai CLAUDE.md is an instructions file published in the GitHub repository miroapp/miro-ai (151 stars, last pushed 10d ago), licensed MIT. It adds 568 tokens to every session, about $0.0028 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-30.
Other instructions, from other repositories
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).
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.
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.
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 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).