Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yezannnnn/agentGroupnpx agentmods add commands/yezannnnn/agentgroup/mermaidWrote 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/commands/yezannnnn/agentgroup/mermaid)<a href="https://agentmods.dev/commands/yezannnnn/agentgroup/mermaid"><img src="https://agentmods.dev/badge/commands/yezannnnn/agentgroup/mermaid.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.00000 | $0.01374 |
| Opus 5 | $0.00000 | $0.00687 |
| Sonnet 5 | $0.00000 | $0.00275 |
| Haiku 4.5 | $0.00000 | $0.00137 |
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 8d 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.
This is a copy
100% identical to mermaid — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create, Update, and Maintain Mermaid Diagrams
Follow these instructions from top to bottom to generate, update, or maintain mermaid diagrams in the project's architecture documentation.
Create a TODO with EXACTLY these 8 items
- Parse arguments and determine action type
- Analyze project structure and existing diagrams
- Identify diagram scope and requirements
- Create or update mermaid diagram code
- Validate diagram syntax and rendering
- Update cross-references and documentation
- Apply diagram standards and styling
- Report results and provide next steps
1 · Parse arguments and determine action type
Check <$ARGUMENTS> to determine the requested action:
- CREATE: Generate new architecture diagrams from scratch
- UPDATE: Modify existing diagrams based on code changes
- MAINTAIN: Review and refresh diagrams for accuracy
- Empty: Analyze project and recommend action
If arguments specify a component/module: Focus on that specific area If arguments are general: Perform comprehensive diagram work
2 · Analyze project structure and existing diagrams
Check existing diagram locations:
All architecture diagrams should be in /docs/architecture/:
docs/architecture/
├── README.md # Main architecture overview
├── context_diagram.md # System context & data flow
├── module_overview.md # Module relationships
└── class_diagrams/
├── core_classes.md # Database, DAOs, data processing
├── data_models.md # Domain models & database schema
└── service_layer.md # UI architecture & service coordination
Analyze the codebase using PARALLEL SUBAGENTS:
- SCAN project structure to understand architecture
- IDENTIFY key components, modules, and services
- CHECK existing diagrams for outdated information
- FIND new additions that need documentation
3 · Identify diagram scope and requirements
Based on analysis, determine what diagrams need work:
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.
- 8d ago First seen · 252 lines · 0 tokens per session scan A 0faab8ef3d5d
mermaid is a command published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,374 tokens. A static security scan graded it A with 0 findings. It is 100% identical to mermaid, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.