flow-diagram

flow-diagram is a skill for Claude Code, Codex from MakingChatbots/genesys-cloud-plugins. It costs 102 tokens per session (1,081 once invoked), scanned A, original, MIT.

A guide for creating flow diagrams with Mermaid, a text format that turns written steps and connections into diagrams. It covers process flows, state machines, dependency maps, and system call sequences.

In plain words
What is it for?
Use it to document pipelines, decision branches, state changes, dependencies, architecture, or calls between systems. It produces static diagrams rather than interactive, pan-and-zoom diagrams.
Why use it?
It helps turn complicated branching processes or system relationships into diagrams that are easy to review and store alongside code and documentation.

Skill for Claude CodeCodex

Part of the genesys-cloud-architect plugin — 3 skills, 1 MCP server shipped together

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.

agentmods
npx agentmods add skills/makingchatbots/genesys-cloud-plugins/flow-diagram
Any agent
npx skills add MakingChatbots/genesys-cloud-plugins --skill flow-diagram
Clone the repo
git clone --depth 1 https://github.com/MakingChatbots/genesys-cloud-plugins

Made for: Claude Code, Codex.

Or install genesys-cloud-architect, the plugin that ships this one along with the rest of its 3 skills, 1 MCP server.

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.

agentmods badge for flow-diagram

README.md
[![agentmods](https://agentmods.dev/badge/skills/makingchatbots/genesys-cloud-plugins/flow-diagram.svg)](https://agentmods.dev/skills/makingchatbots/genesys-cloud-plugins/flow-diagram)
Your own site
<a href="https://agentmods.dev/skills/makingchatbots/genesys-cloud-plugins/flow-diagram"><img src="https://agentmods.dev/badge/skills/makingchatbots/genesys-cloud-plugins/flow-diagram.svg" alt="Measured on agentmods" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,081 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00102 $0.01081
Opus 5 $0.00051 $0.00541
Sonnet 5 $0.00020 $0.00216
Haiku 4.5 $0.00010 $0.00108

Measured 3d ago against content hash 6f56a22cef99, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

flow-diagram 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 3d 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.

skills/flow-diagram/SKILL.md · 89 lines

How it starts

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

Flow Diagram Skill

Create flow diagrams as Mermaid — text-based with automatic layout. Mermaid is diffable, cheap to generate, and renders natively in GitHub markdown (READMEs, PR and issue descriptions), Claude artifacts, and most docs tooling.

For graphs with fewer than 3 nodes or no edges, prefer plain text (ASCII or a markdown table) — not worth a diagram.

Workflow

1. Pick the diagram type

Data Mermaid type
Flows, pipelines, decision branches flowchart TD (or LR for wide/shallow graphs)
State machines stateDiagram-v2
Dependencies, architecture maps flowchart LR with subgraph groupings
Sequences of calls between systems sequenceDiagram

2. Write the diagram

flowchart TD
    Welcome["Welcome message"] --> Hours{"Business hours?"}
    Hours -->|open| Queue["Route to Sales queue"]
    Hours -->|closed| AfterHours["After-hours message"]
    AfterHours --> Offer{"Leave a voicemail?"}
    Offer -->|yes| Record["Record voicemail"]
    Offer -->|no| Finish["End call"]
    Queue --> Finish
    Record --> Finish

Syntax gotchas:

  • Quote any label containing parentheses, colons, or other punctuation: A["Play message (after hours)"]
  • end (lowercase) is a reserved word in flowcharts — use a different node id like Finish
  • Edge labels use pipes: A -->|open| B
  • Colour node categories with classDef + class, e.g. classDef queue fill:#1d4ed8,color:#fff then class Queue queue

3. Deliver it where it will actually render

Mermaid source is only a picture where something renders it. A fenced block printed into a Claude Code terminal shows as raw source text, not a diagram — so pick the delivery form from the destination:

Destination Deliver as
GitHub PR or issue description, README, a committed .md file Fenced ```mermaid block — inline in the response for the user to paste, or written to the file
The user wants to look at the diagram now, in a Claude Code session ("show me", "let me see it") A standalone HTML file they can open (section 5), or a published Artifact — never bare source in the terminal
Web or desktop chat, or docs tooling that renders Mermaid Fenced ```mermaid block

Read the full file on GitHub · 89 lines

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.

  1. 3d ago First seen · 89 lines · 102 tokens per session scan A 6f56a22cef99

Subscribe to this mod's changes

flow-diagram is a skill published in the GitHub repository MakingChatbots/genesys-cloud-plugins (9 stars, last pushed 3d ago), licensed MIT. It adds 102 tokens to every session and 1,081 once invoked, about $0.0005 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-31.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens