architecture-diagram

architecture-diagram is a skill for Claude Code from konraddzbik/architecture-diagram-skill. It costs 203 tokens per session (4,964 once invoked), scanned A, original, MIT.

A skill for building a self-contained interactive HTML diagram of a software system. It can show step-by-step flows, data details, and selectable operating modes such as development or production.

In plain words
What is it for?
Use it to explain authentication, service communication, data pipelines, deployment flows, or agent tool calls. It also creates a companion Markdown description.
Why use it?
It makes complex system behavior easier to explore during workshops and onboarding. The diagram can show how data moves between services instead of relying only on a static picture.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions Gemini CLI; mentions OpenCode.

Part of the architecture-diagram-skill plugin — 1 skill shipped together

Good fit Use it to explain authentication, service communication, data pipelines, deployment flows, or agent tool calls. It also creates a companion Markdown description.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/konraddzbik/architecture-diagram-skill/architecture-diagram
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.

Any agent
npx skills add konraddzbik/architecture-diagram-skill --skill architecture-diagram
Clone the repo
git clone --depth 1 https://github.com/konraddzbik/architecture-diagram-skill

Made for: Claude Code.

Or install architecture-diagram-skill, the plugin that ships this one along with the rest of its 1 skill.

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 architecture-diagram

README.md
[![agentmods](https://agentmods.dev/badge/skills/konraddzbik/architecture-diagram-skill/architecture-diagram/github.svg)](https://agentmods.dev/skills/konraddzbik/architecture-diagram-skill/architecture-diagram)
Your own site
<a href="https://agentmods.dev/skills/konraddzbik/architecture-diagram-skill/architecture-diagram"><img src="https://agentmods.dev/badge/skills/konraddzbik/architecture-diagram-skill/architecture-diagram/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.

agentmods 80×15 button for architecture-diagram

Your own site · 80×15
<a href="https://agentmods.dev/skills/konraddzbik/architecture-diagram-skill/architecture-diagram"><img src="https://agentmods.dev/badge/skills/konraddzbik/architecture-diagram-skill/architecture-diagram.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 203 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,964 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high YARA Match · line 4
    YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
    Fix: Remove offensive tool references and exploit code. Legitimate agent skills should not contain penetration testing tools, exploit frameworks, or reconnaissance utilities.
  • medium Rogue Agent · line 283
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
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.1 $0.00203 $0.04964
Opus 5 $0.00102 $0.02482
Sonnet 5 $0.00041 $0.00993
Haiku 4.5 $0.00020 $0.00496

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

Security

Grade A, and why

architecture-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 13d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (references/screenshot.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/architecture-diagram/SKILL.md · 310 lines

How it starts

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

Interactive Architecture Diagrams

Build single-file, drop-in HTML pages that let workshop attendees, clients, or new team members click through how a system works — step by step, with animated data packets flowing between nodes, payload details on a side panel, and toggleable modes (offline/online, dev/prod, v1/v2). The aesthetic is dark and didactic-first: bounded nodes, gentle quadratic wires, packets that glow only on the active step — no rainbow gradients. Rebrand via the CSS tokens in assets/css-tokens.css.


When to reach for this skill

Situation Use this skill?
"Show me how the auth flow works" (interactive, for a workshop) Yes
"Design the RAG pipeline before we build it" (planning new service) Yes
"Map our microservices and how they communicate" Yes
"Visualize the CI/CD pipeline for onboarding docs" Yes
"Show the data flow through our ETL pipeline" Yes
"Draw an agentic multi-agent system with tool calls" Yes
"Build me an architecture mockup we can iterate on with the team" Yes
"Draw a sequence diagram for the PR" (static, goes in markdown) No — a Mermaid sequence diagram inline is simpler
"Add a diagram to a slide deck or PDF" (static, not interactive) No — this produces interactive HTML, not images or slides
"I just need a static boxes-and-arrows topology" (no flows/steps) No — a Mermaid flowchart is enough

The differentiator is interactivity + sequenced data flow: if the value is "click through it and watch what happens", use this skill; if you need a static image, a slide, or an inline diagram, use Mermaid instead.


The mental model

Every diagram has four things:

  1. Nodes — services, datastores, users, queues, external systems. Each has a role (color) and metadata (tech stack, port, deployment target).
  2. Flows — named scenarios the user can pick (e.g. RAG Query, Direct Query, Ingest, Auth). Each flow is an ordered list of steps.
  3. Steps{from, to, color, title, route, payload, desc, chips}. Each step lights up one wire and one target node. (color and title are required — a missing color leaves the wire uncolored, a missing title leaves the panel header blank.)
  4. Modes — orthogonal toggle (offline/online, dev/prod, v1/v2). Modes can:
    • hide/show entire nodes (e.g. Seed only exists offline)
    • rename a node (Qdrant → BigQuery)
    • swap payload bodies, ports, auth headers, latency chips

Read the full file on GitHub · 310 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. 13d ago First seen · 310 lines · 203 tokens per session scan A a7cafa547c15

Subscribe to this mod's changes

architecture-diagram is a skill published in the GitHub repository konraddzbik/architecture-diagram-skill (89 stars, last pushed 1mo ago), licensed MIT. It adds 203 tokens to every session and 4,964 once invoked, about $0.0010 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.