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 skills add tslateman/duet --skill mermaidgit clone --depth 1 https://github.com/tslateman/duetWrote 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/skills/tslateman/duet/mermaid)<a href="https://agentmods.dev/skills/tslateman/duet/mermaid"><img src="https://agentmods.dev/badge/skills/tslateman/duet/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.
<a href="https://agentmods.dev/skills/tslateman/duet/mermaid"><img src="https://agentmods.dev/badge/skills/tslateman/duet/mermaid.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.00067 | $0.00775 |
| Opus 5.5 | $0.00027 | $0.00310 |
| Sonnet 5.5 | $0.00013 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00077 |
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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mermaid.js v11
Overview
Mermaid is the only diagram format that renders natively in GitHub markdown: no exported images to commit.
Quick Start
Basic Diagram Structure:
{diagram-type}
{diagram-content}
Common Diagram Types:
flowchart- Process flows, decision treessequenceDiagram- Actor interactions, API flowsclassDiagram- OOP structures, data modelsstateDiagram- State machines, workflowserDiagram- Database relationshipsgantt- Project timelinesjourney- User experience flows
WARNING:
references/diagram-types.mdcovers all 24+ diagram types with full syntax. Load only when you need a specific type's syntax.
Creating Diagrams
Inline Markdown Code Blocks:
```mermaid
flowchart TD
A[Start] --> B{Decision}
B -->|Yes| C[Action]
B -->|No| D[End]
```
Configuration via Frontmatter:
```mermaid
---
theme: dark
---
flowchart LR
A --> B
```
Comments: Use %% prefix for single-line comments.
Syntax Rules
Follow these to avoid parse errors:
- Indentation: Use consistent 4-space indentation
- Node IDs: Short unique identifiers (A, B, node1). Avoid reserved words
- Special characters: Wrap text with special characters in quotes
- Subgraphs: Must close with
endkeyword - Whitespace: No trailing whitespace (causes parsing failures)
- Complexity: Break diagrams at 15+ elements into multiple focused diagrams
CLI Usage
Convert .mmd files to images:
# Installation
npm install -g @mermaid-js/mermaid-cli
# Basic conversion
mmdc -i diagram.mmd -o diagram.svg
# With theme and background
mmdc -i input.mmd -o output.png -t dark -b transparent
# Custom styling
mmdc -i diagram.mmd --cssFile style.css -o output.svg
See references/cli-usage.md for Docker, batch processing, and advanced workflows. To render from JavaScript instead of the CLI, see references/integration.md for the API and embedding.
What ships with it
5 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.
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 · 118 lines · 67 tokens per session scan A 1cd6bb816eb8
mermaid is a skill published in the GitHub repository tslateman/duet (1 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 775 once invoked, about $0.0003 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-31.
Other skills, from other repositories
skill-design-lineage
Persist design documents with branch tracking, revision chains, and cross-session discovery.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
recipe-front-design
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval.
recipe-front-adjust
Adjust an already-implemented UI in-session with verification against the design source.
claude-code-bash-patterns
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.
git-workflow
Manages branches, worktrees, atomic commits, and branch completion by merge, PR, preserve, or discard. Use when starting feature work that needs a branch or an isolated workspace, making commits during development, or finishing a development branch. Also use when the user says "set up worktree", "create PR", "finish…