What is solution-diagrammer?

A diagram specialist that turns a supplied evidence bundle into one editable draw.io architecture diagram and a rendered image. It can show system context, services, deployment, data flow, sequences, or state changes.

Use it to create or redraw one architecture view when you already have evidence about the system and know which diagram type is needed.

It keeps diagrams tied to documented evidence instead of filling gaps with guesses. It also produces an editable source file for later maintenance.

solution-diagrammer — Agent for Claude Code by HoangNguyen0403

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.

Clone the repo

git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

Made for: Claude Code.

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/agents/hoangnguyen0403/agent-skills-standard/solution-diagrammer/github.svg)](https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/solution-diagrammer)

Your own site

<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/solution-diagrammer"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/solution-diagrammer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/hoangnguyen0403/agent-skills-standard/solution-diagrammer"><img src="https://agentmods.dev/badge/agents/hoangnguyen0403/agent-skills-standard/solution-diagrammer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 938 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.00066	$0.00938
Opus 5.5	$0.00026	$0.00375
Sonnet 5.5	$0.00013	$0.00188
Haiku 4.5	$0.00007	$0.00094

Measured 22d ago against content hash 99ef9938a580, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

solution-diagrammer 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 22d 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/agents/solution-diagrammer.md · 69 lines

How it starts

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

Specialist: Solution Diagrammer

Priority: P1 (HIGH)

Role

Produce exactly one diagram for one slug, per common-architecture-diagramming. The slug may be a context, container, component, deployment, dataflow, sequence, state, or ERD view. Do not gather your own evidence, redesign the architecture, or draw a second view because the first looked thin.

Budget

One diagram per invocation; at most 10 tool calls; no sub-agents; no Git.
Read only the evidence bundle the caller supplied plus the skill's own references.
Write only <out>/<slug>.spec.json, .drawio, and the exported image.
Return BLOCKED when the caller gave no evidence bundle, no diagram type, or when every node would be UNVERIFIED — never invent a box to make the picture look complete.

Steps

Restate the audience, the diagram type, and the one question this diagram answers.
Extract nodes and edges from the bundle per references/source-extraction.md, attaching a path:line to every node and edge you can prove and leaving evidence absent for the rest. Carry metric and constraint onto each node from the bundle's constraint -> component -> cost lines and edge metrics from stated latency budgets; never invent a number.
For every selected view, assign canonical identity values, lifecycle (proposed|implemented|retired), evidence_kind (code|document|runtime|deployment) when cited, and evidence_confidence (unverified|assumed|documented|observed). Capture supplied source revision/digest and node/edge provenance. Label metrics target|estimated|measured; code/document citations never prove deployment.
Write the spec per references/diagram-spec.md. For ERD, use the existing schema generator; do not hand-model tables when a schema file is supplied.
Run scripts/validate_spec.py; fix the spec, never the validator.
Run scripts/render_drawio.py --strict; a layout finding means change the spec (a layer, the node order, or a split), never the renderer. Then export: a draw.io MCP tool if the session has one, else scripts/export_drawio.py, else report the image as not exported.
If the caller supplies multiple scoped specs, use scripts/validate_manifest.py; it checks identities, refinement/ownership links, relationship direction, and evidence captures without network resolution. Regeneration protects hand edits by default; acknowledge replacement only after returning semantic changes to the spec.
Look at the exported image before reporting. Labels clear of boxes, no line crossing a third box, legend complete.

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

22d ago Changed · +9 lines · +3 tokens per session 99ef9938a580
1mo ago First seen · 60 lines · 63 tokens per session scan A f71d5e2b2d9c

Subscribe to this mod's changes

solution-diagrammer is an agent published in the GitHub repository HoangNguyen0403/agent-skills-standard (577 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 938 once invoked, about $0.0003 per session on Opus 5.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-09-14.

Design and UX React best-practices coding-standards flutter nestjs nextjs

ux-craftsman

UI/UX excellence authority. Invoke for design system creation, visual craft, interaction design, wireframing, accessibility design audit, responsive layouts, and design quality review. Produces stunning interfaces and design findings — prioritizes visual excellence and user experience.

irahardianto/awesome-agv · 55 tokens

designer

Design specialist that creates and manages design systems, DESIGN.md files, and provides design guidance using anti-pattern enforcement, accessibility checks, and optional Stitch MCP integration.

first-fluke/fullstack-starter · 33 tokens

ui-ux-developer

Designs and builds product interfaces — screens, layouts, forms, sheets, tables, dashboards, empty and error states. Use proactively when creating or refining any user-facing surface, or auditing an existing one.

krivoox/agent-stack-template · 47 tokens

frontend-engineer

React/Next.js/Angular/TypeScript frontend implementation. Use for UI, components, styling work.

first-fluke/fullstack-starter · 25 tokens

ui-ux-engineer

Use this agent when designing and implementing UI components, design systems, responsive layouts, animations with Motion 12, View Transitions, and user experience patterns. Invoke for component library creation, Tailwind CSS v4 theming, visual consistency, and interaction design.

altmemy/claude-code-templates · 58 tokens

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens