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.
git clone --depth 1 https://github.com/olgasafonova/miro-mcp-serverWrote 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/rules/olgasafonova/miro-mcp-server/miro-best-practices)<a href="https://agentmods.dev/rules/olgasafonova/miro-mcp-server/miro-best-practices"><img src="https://agentmods.dev/badge/rules/olgasafonova/miro-mcp-server/miro-best-practices/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/rules/olgasafonova/miro-mcp-server/miro-best-practices"><img src="https://agentmods.dev/badge/rules/olgasafonova/miro-mcp-server/miro-best-practices.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.00197 | $0.00197 |
| Opus 5 | $0.00098 | $0.00098 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
miro-best-practices 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 10d 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.
What it actually says
Miro tool usage guardrails
- Always call
miro_list_boardsfirst to discover board IDs before any board operation. - Save item IDs returned from creation tools; you need them for connectors and updates.
- Use
miro_bulk_createwhen adding 3 or more items instead of multiple individual create calls. - Give short confirmations after actions: "Added 5 stickies to Design Board" not verbose summaries.
- Use
miro_search_boardto find existing content before creating duplicates. - When generating diagrams, use
miro_generate_diagramwith Mermaid syntax (flowchart or sequenceDiagram). - Sticky colors: yellow, green, blue, pink, orange, red, gray, cyan, purple, dark_green, dark_blue, black.
- Common shapes: rectangle, round_rectangle, circle, triangle, rhombus, star, hexagon, pentagon.
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.
- 10d ago First seen · 15 lines · 197 tokens per session scan A 144f20a9878b
miro-best-practices is a cursor rule published in the GitHub repository olgasafonova/miro-mcp-server (26 stars, last pushed today), licensed MIT. It adds 197 tokens to every session, about $0.0010 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 cursor rules, from other repositories
wiki-safety
MCP server for MediaWiki wikis - search, read, and edit wiki content from AI assistants.
go-conventions
Go conventions for all Go code (modules, naming, errors, logging, metrics).
go-project-structure
This rule ensures that Go projects follow a consistent and idiomatic structure, making the codebase easier to navigate, maintain, and scale.
go-testing-practices
Go Testing Best Practices.
go-patterns
Go idioms, error handling, and tooling conventions.
golang-files
Cursor rule "golang-files" from MairwunNx/xi, covering go files (.go) rules, language version & features, code style, package organization and error handling.