A command that creates simple text-based diagrams from the current conversation or implementation context. It can show data movement, component structure, state changes, or step-by-step interactions.

Use it to diagram data flows, React component trees, state machines, permission flows, sessions, payments, or other discussed system behavior.

It makes architecture and implementation decisions easier to understand when a written explanation is not enough.

How FlorianBruniaux/ccboard configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to FlorianBruniaux/ccboard. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/FlorianBruniaux/ccboard/main/.claude/commands/diagram.md

Clone the repo

git clone --depth 1 https://github.com/FlorianBruniaux/ccboard

Made for: Claude Code.

Or install ccboard, the plugin that ships this one along with the rest of its 14 skills, 2 commands, 10 agents, 4 hooks, 2 MCP servers.

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/commands/florianbruniaux/ccboard/diagram.svg)](https://agentmods.dev/commands/florianbruniaux/ccboard/diagram)

Your own site

<a href="https://agentmods.dev/commands/florianbruniaux/ccboard/diagram"><img src="https://agentmods.dev/badge/commands/florianbruniaux/ccboard/diagram.svg" alt="Measured on agentmods" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 980 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.

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.00013	$0.00980
Opus 5	$0.00006	$0.00490
Sonnet 5	$0.00003	$0.00196
Haiku 4.5	$0.00001	$0.00098

Measured 8d ago against content hash e52e59e0e4ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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

.claude/commands/diagram.md · 154 lines

How it starts

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

/diagram

Analyse le contexte de la conversation et genere 1-3 diagrammes ASCII pertinents.

Arguments

$ARGUMENTS : Optionnel. Focus sur un aspect specifique (ex: "permission flow", "session states")

Comportement

Analyser le contexte conversation (ce qui a ete implemente/discute dans la session)
Si $ARGUMENTS fourni : focus sur cet aspect specifique
Si contexte ambigu et pas d'arguments : poser UNE question via AskUserQuestion

question: "Quel aspect de l'implementation veux-tu diagrammer ?"
header: "Diagram"
options:
  - label: "Data flow"
    description: "Client → Router → Service → Repository → DB"
  - label: "Component tree"
    description: "Hierarchie composants React impactes"
  - label: "State machine"
    description: "Transitions d'etats (sessions, payments, etc.)"
  - label: "Sequence"
    description: "Interactions entre acteurs/systemes"

Generer 1-3 diagrammes ASCII selon le type de changement
Chaque diagramme avec une legende courte (1-2 lignes max)

Types de diagrammes

Choisir le(s) type(s) le(s) plus pertinent(s) selon le contexte :

Data Flow (changements backend, 3-tier)

Client ──→ Router ──→ Service ──→ Repository ──→ DB
             │           │
             │       Permission
             │        Check
           Zod
         Validation

Component Tree (changements frontend)

src/
├── components/
│   ├── session-card.tsx     ← modified
│   └── session-list.tsx     ← modified
└── server/
    └── api/
        └── routers/session.ts ← modified

State Machine (workflows, status transitions)

SCHEDULED ──→ STARTED ──→ COMPLETED
    │                        ↑
    └──→ CANCELLED           │
                    STARTED ─┘

Sequence (interactions multi-acteurs)

User          Frontend        tRPC           Service
 │──── click ────→│              │               │
 │               │── mutation ──→│               │
 │               │              │── validate ──→│
 │               │              │←── result ────│
 │←── toast ─────│              │               │

Read the full file on GitHub · 154 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.

8d ago First seen · 154 lines · 13 tokens per session scan A e52e59e0e4ec

Subscribe to this mod's changes

diagram is a command published in the GitHub repository FlorianBruniaux/ccboard (97 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 980 once invoked, about $0.0001 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-30.

Analytics and metrics Claude Code Planning anthropic budget-alerts cli context-engineering

atomic-plan

Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.

damusix/atomic-claude · 54 tokens

ccboard: Command for Claude Code