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.
git clone --depth 1 https://github.com/tjboudreaux/cc-plugin-text-visualizationsWrote 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/tjboudreaux/cc-plugin-text-visualizations/diagram)<a href="https://agentmods.dev/commands/tjboudreaux/cc-plugin-text-visualizations/diagram"><img src="https://agentmods.dev/badge/commands/tjboudreaux/cc-plugin-text-visualizations/diagram.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.00018 | $0.01426 |
| Opus 5 | $0.00009 | $0.00713 |
| Sonnet 5 | $0.00004 | $0.00285 |
| Haiku 4.5 | $0.00002 | $0.00143 |
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 6d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagram Generation
Create diagram: $ARGUMENTS
Instructions
Parse the arguments to determine diagram type and subject, then generate appropriate visualization.
Diagram Types
1. Flowchart
Trigger: "flow", "flowchart", "process", "workflow"
/diagram flow <process to visualize>
- Apply
tools-visual-workflowsfor ASCII flowcharts - Apply
tools-mermaidfor rendered diagrams - Output: Both ASCII and Mermaid versions
2. Architecture
Trigger: "arch", "architecture", "system", "components"
/diagram arch <system to visualize>
- Apply
tools-visual-ascii-archfor ASCII architecture - Apply
tools-mermaidfor rendered diagrams - Output: Layered architecture diagram
3. State Machine
Trigger: "state", "states", "transitions", "fsm"
/diagram state <entity and states>
- Apply
tools-visual-state-machinesfor state diagrams - Apply
tools-mermaidfor rendered version - Output: State transition diagram
4. Timeline
Trigger: "timeline", "sequence", "time", "phases"
/diagram timeline <process with phases>
- Apply
tools-visual-workflowsfor timeline - Output: ASCII timeline diagram
5. Mermaid Only
Trigger: "mermaid", "md", "markdown"
/diagram mermaid <diagram description>
- Apply
tools-mermaidfor Mermaid syntax - Output: Mermaid code block for markdown
6. Retrospective
Trigger: "retro", "retrospective", "review"
/diagram retro <what to review>
- Apply
tools-visual-retrofor retro grids - Output: Retrospective visualization
7. Cheatsheet
Trigger: "cheat", "cheatsheet", "reference", "commands"
/diagram cheat <tool or topic>
- Apply
tools-visual-cheatsheetsfor command panels - Output: ASCII command reference
Output Formats
ASCII Flowchart
┌─────────────────┐
│ Start │
└────────┬────────┘
│
▼
┌─────────────────┐
│ Process A │
└────────┬────────┘
│
┌────┴────┐
│ Decision │
└────┬────┘
┌────┴────┐
yes no
│ │
▼ ▼
┌───────┐ ┌───────┐
│ Path A│ │ Path B│
└───────┘ └───────┘
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.
- 6d ago First seen · 194 lines · 0 tokens per session scan A 7591f954503c
diagram is a command published in the GitHub repository tjboudreaux/cc-plugin-text-visualizations (2 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,426 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-31.
Other commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
team-ui
Orchestrate UI/UX design team.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.