A diagram generator that turns code, system designs, data relationships, and processes into Mermaid diagrams, which are text-based diagrams that can be rendered in documentation and tools.

Use it to create flowcharts, request sequences, class diagrams, database relationship diagrams, state machines, dependency graphs, and other Mermaid visualizations.

It makes complicated flows and structures easier to inspect and explain than prose alone. It also helps choose a diagram type that matches the subject.

visualize — Skill for Claude Code and Codex by heyAyushh: A diagram generator that turns code, system designs, data…

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/heyayushh/stacc/visualize

Any agent

npx skills add heyAyushh/stacc --skill visualize

Clone the repo

git clone --depth 1 https://github.com/heyAyushh/stacc

Made for: Claude Code, Codex.

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/skills/heyayushh/stacc/visualize.svg)](https://agentmods.dev/skills/heyayushh/stacc/visualize)

Your own site

<a href="https://agentmods.dev/skills/heyayushh/stacc/visualize"><img src="https://agentmods.dev/badge/skills/heyayushh/stacc/visualize.svg" alt="Measured on agentmods" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Model	Per session	Once invoked
Fable 5	$0.00045	$0.00450
Opus 5	$0.00023	$0.00225
Sonnet 5	$0.00009	$0.00090
Haiku 4.5	$0.00005	$0.00045

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

Security

Grade A, and why

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

configs/commands/skills/visualize/SKILL.md · 57 lines

What it actually says

Visualize - Generate Mermaid Diagram

Analyze input and generate clear, well-structured Mermaid diagrams.

Workflow

Analyze input - Understand what to visualize (code flow, architecture, data relationships, state machines, sequences, etc.)
Choose diagram type:
- flowchart - Process flows, decision trees, algorithms
- sequenceDiagram - API calls, message passing, request/response
- classDiagram - Class structures, inheritance, interfaces
- erDiagram - Database schemas, entity relationships
- stateDiagram-v2 - State machines, lifecycle flows
- graph TD/LR - Dependency graphs, module relationships
- gitgraph - Git branching strategies
- journey - User journeys
- gantt - Timelines and schedules
Generate diagram with:
- Clear, descriptive node labels
- Logical grouping with subgraphs where appropriate
- Consistent styling and direction
- Meaningful relationship labels on edges
- Manageable complexity (split if needed)
Output in mermaid code block:
```
```mermaid
[diagram code]
```
```

Style Guidelines

Use descriptive IDs: userService not a1
Add labels to relationships when they add clarity
Use subgraphs to group related components
Keep readable: max ~15-20 nodes per diagram
Arrow styles:
- --> solid (main flow)
- -.-> dotted (optional/async)
- ==> thick (important path)
- o--> circle end (aggregation)
- *--> diamond end (composition)

After Generating

Explain what the diagram shows
Offer to refine or expand specific sections
Suggest alternative diagram types if applicable

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.

3d ago First seen · 57 lines · 45 tokens per session scan A 384c26110740

Subscribe to this mod's changes

visualize is a skill published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 450 once invoked, about $0.0002 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.

Planning

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