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.
/plugin marketplace add Yesterday-AI/skillsnpx agentmods add plugins/yesterday-ai/skills/miro-boardgit clone --depth 1 https://github.com/Yesterday-AI/skillsWrote 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/plugins/yesterday-ai/skills/miro-board)<a href="https://agentmods.dev/plugins/yesterday-ai/skills/miro-board"><img src="https://agentmods.dev/badge/plugins/yesterday-ai/skills/miro-board.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
miro-board 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 today.
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
{
"name": "miro-board",
"description": "Create and read Miro board content via MCP tools. Diagrams (flowcharts, mindmaps, UML, ER), documents (markdown), tables, and context extraction.",
"author": {
"name": "Yesterday"
},
"homepage": "https://github.com/Yesterday-AI/skills/tree/main/.compiled/skill-plugins/miro-board",
"repository": "https://github.com/Yesterday-AI/skills",
"license": "MIT",
"keywords": [
"claude-code",
"yesterday",
"miro",
"diagrams",
"mcp",
"whiteboard"
]
}
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.
- today Changed · +18 lines a83accd61d70
- 5d ago First seen · 1 lines scan A e429eea7758d
miro-board is a plugin published in the GitHub repository Yesterday-AI/skills (2 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
kage
Kage manages your memory and agents. It briefs and runs agents in isolated git worktrees for a single run or a multi-wave goal, re-runs the checks itself instead of trusting the agent's report, and remembers what it learns so each brief is smarter than the last.
mosaic-bridge
Mosaic Bridge — Unity MCP assistant agents for scene building, shader creation, and session continuity.
peer-review-jj
Unified change review for jj repos — generalist-first with emergent specialists, two-phase pipeline, structured findings.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.