architecture-diagrams

architecture-diagrams is a skill for Claude Code from sananthanarayan/skilldrop. It costs 72 tokens per session (1,056 once invoked), scanned A, original, MIT.

A diagram-writing skill that turns a written system description into a visual map of its parts and connections. It supports common diagram formats for cloud systems, service interactions, data models, workflows, and software structure.

In plain words
What is it for?
Use it to create cloud architecture maps, service call sequences, C4 diagrams, database relationship diagrams, workflow state diagrams, class diagrams, or UML-style diagrams.
Why use it?
It removes the need to work out the diagram syntax by hand. It also helps choose a diagram type that matches what you want to explain, such as request order or database relationships.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the skilldrop plugin — 51 skills, 4 agents shipped together

Good fit Use it to create cloud architecture maps, service call sequences, C4 diagrams, database relationship diagrams, workflow state diagrams, class diagrams, or UML-style diagrams.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sananthanarayan/skilldrop/architecture-diagrams
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 sananthanarayan/skilldrop --skill architecture-diagrams
Clone the repo
git clone --depth 1 https://github.com/sananthanarayan/skilldrop

Made for: Claude Code.

Or install skilldrop, the plugin that ships this one along with the rest of its 51 skills, 4 agents.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/sananthanarayan/skilldrop/architecture-diagrams"><img src="https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/architecture-diagrams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,056 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.01056
Opus 5 $0.00036 $0.00528
Sonnet 5 $0.00014 $0.00211
Haiku 4.5 $0.00007 $0.00106

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

Security

Grade A, and why

architecture-diagrams 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 10d 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.

skills/architecture-diagrams/SKILL.md · 67 lines

How it starts

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

architecture-diagrams

You help the user turn a written system description into a clean, renderable architecture diagram.

How to respond

  1. Clarify only what blocks correctness. Before drawing, you may ask 1–2 short questions if the description is missing something load-bearing (e.g., "Is auth synchronous or via a sidecar?"). Don't pepper the user with questions for taste preferences — pick a reasonable default and call it out.

  2. Pick the right notation. Use this rough mapping unless the user requests otherwise:

    User's intent Use
    Cloud architecture (AWS/Azure/GCP) — boxes, arrows, services Mermaid flowchart or graph
    Request flow across services / call order matters Mermaid sequenceDiagram
    Strategic / multi-level view (context → container → component) C4 (PlantUML !include c4)
    Data model, tables, relationships Mermaid erDiagram
    State machine / workflow Mermaid stateDiagram-v2
    Class / type hierarchy Mermaid classDiagram
    Looks-pretty UML-style for slides PlantUML
  3. Output the diagram in a fenced code block with the correct language tag (```mermaid, ```plantuml). Then add 2–4 bullet points underneath explaining the key design choices ("Why two ECS services and not one?") so the diagram is reviewable, not just renderable.

  4. Offer next steps, e.g., "Want me to export this as SVG via the Mermaid CLI?" or "Want me to push this into a Figma file? (use the figma-diagrams skill)".

Useful references in this skill

When you need a starting shape, copy from one of the templates rather than inventing notation from scratch — it cuts down on syntax errors and keeps style consistent across diagrams.

Read the full file on GitHub · 67 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. 10d ago First seen · 67 lines · 72 tokens per session scan A 835ed396d1c3

Subscribe to this mod's changes

architecture-diagrams is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 26d ago), licensed MIT. It adds 72 tokens to every session and 1,056 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

options

Present multiple design options as a vertical stack of anchored turns.

asgeirtj/system_prompts_leaks · 13 tokens

qa-test-planner

Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.

davila7/claude-code-templates · 34 tokens

visualize

Render a polished visual inline in the chat as part of your answer — a diagram, a chart, an interactive explainer, or a UI mockup. Load it proactively whenever an explanation would land better as a picture than as prose. Do not wait to be asked.

vellum-ai/vellum-assistant · 57 tokens

journey-mapping

Build customer journey maps and service blueprints that visualize the end-to-end user experience including touchpoints, emotions, friction, and underlying systems. Use this skill whenever the user wants to map a customer journey, build a service blueprint, identify friction across an experience, align teams on the…

rampstackco/claude-skills · 131 tokens

ux-design

Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.

Donchitos/Claude-Code-Game-Studios · 61 tokens

layout-skill

Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…

code-yeongyu/oh-my-openagent · 88 tokens