A tool for creating Mermaid diagrams, which are text-based diagrams for showing workflows, system structures, data relationships, schedules, and other processes.

Use it to create flowcharts, sequence diagrams, class diagrams, entity-relationship diagrams, state diagrams, timelines, architecture diagrams, and other supported Mermaid formats.

It turns written requirements or explanations into visual maps that are easier to inspect and discuss.

mermaid — Skill for Claude Code by giang6283623

Install

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.

Any agent

npx skills add giang6283623/minimal-vibe-coding-kit --skill mermaid

Clone the repo

git clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/mermaid/github.svg)](https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/mermaid)

Your own site

<a href="https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/mermaid"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/mermaid/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/mermaid"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/mermaid.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,531 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00095	$0.02531
Opus 5.5	$0.00038	$0.01012
Sonnet 5.5	$0.00019	$0.00506
Haiku 4.5	$0.00010	$0.00253

Measured 2mo ago against content hash 5676fb48148b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mermaid 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 2mo 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.

.agents/skills/mermaid/SKILL.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mermaid Diagram Generator

Maintained by Minimal Vibe Coding Kit. Generate high-quality Mermaid diagram code, styled by default with the Vivid Clay preset, matched to the reader's coding level.

Workflow

Understand requirements: analyze the request to determine the most suitable diagram type.
Match the coding level: read references/coding-level-charts.md and shape the diagram to the active /coding-level (or the Default coding level in backbone.yml conventions.custom_rules; level 2-3 conventions when none is set).
Read the type reference: open the syntax reference for the chosen diagram type from the table below.
Generate code: produce Mermaid code following that specification.
Apply styling: read styling-preset.md, find the diagram type in its coverage table, and apply exactly the mechanism that row names (universal frontmatter block plus the type's own section when it has one). Merge additions into the existing config and themeVariables mappings; never paste a second mapping with either key. Skip only if the user asks for plain output or names another theme.
Apply safety defaults: keep Mermaid's strict security mode, do not emit callbacks or remote media from untrusted input, and use only user-approved links.
Validate honestly: before parsing, verify that every YAML frontmatter key is unique within its mapping scope, especially config and themeVariables. Treat any duplicate-key warning as a failure. Then parse or render when trusted tooling is available. Otherwise label the output syntax-reviewed and never claim visual verification.

Kit Triggers - offer, don't assume

Document generation: when asked to produce documentation with a flow, structure, ownership map, or state change involving at least three materially related parts, and diagrams were not mentioned, ask once before writing: "Include Mermaid diagrams to illustrate this? (yes/no)". Do not interrupt a small copy edit or a one-fact document. Respect the answer for the whole document. If the session cannot ask (autonomous run), include diagrams only where the relationship is genuinely clearer as a picture, and say so.
Debugging / failure analysis: when a root cause is being traced across at least three workflow steps or components, offer once: "Want a visual workflow chart with the risky zones highlighted in red? (yes/no)". Do not offer for a single-line or already-isolated failure. On yes, follow debug-heatmap.md to render the flow with evidence-ranked suspect zones.
Never repeat a declined offer within the same task.

Read the full file on GitHub · 143 lines

Files

What ships with it

44 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

2mo ago First seen · 143 lines · 95 tokens per session scan A 5676fb48148b

Subscribe to this mod's changes

mermaid is a skill published in the GitHub repository giang6283623/minimal-vibe-coding-kit (26 stars, last pushed 18d ago), licensed MIT. It adds 95 tokens to every session and 2,531 once invoked, about $0.0004 per session on Opus 5.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.

Writing and docs

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.