system-design-diagramming

system-design-diagramming is a skill for Claude Code, Codex from HoangNguyen0403/agent-skills-standard. It costs 63 tokens per session (863 once invoked), scanned A, original, MIT.

Instructions for drawing system diagrams in the Archify visual style, using typed JSON specifications rendered as SVG images. It covers architecture, workflows, sequences, data flows, and lifecycles.

In plain words
What is it for?
Use it to create and validate diagrams of system components, processes, request chains, pipelines, or state changes.
Why use it?
It keeps diagram structure, colors, labels, validation, and rendering rules consistent.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to create and validate diagrams of system components, processes, request chains, pipelines, or state changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hoangnguyen0403/agent-skills-standard/system-design-diagramming
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 HoangNguyen0403/agent-skills-standard --skill system-design-diagramming
Clone the repo
git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard

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.

agentmods badge for system-design-diagramming

README.md
[![agentmods](https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/system-design-diagramming/github.svg)](https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/system-design-diagramming)
Your own site
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/system-design-diagramming"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/system-design-diagramming/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 system-design-diagramming

Your own site · 80×15
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/system-design-diagramming"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/system-design-diagramming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 863 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 pass 7 Sept 2026
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.00063 $0.00863
Opus 5 $0.00032 $0.00432
Sonnet 5 $0.00013 $0.00173
Haiku 4.5 $0.00006 $0.00086

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

Security

Grade A, and why

system-design-diagramming 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.

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.

.agents/skills/system-design/system-design-diagramming/SKILL.md · 73 lines

How it starts

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

System Diagramming (Archify Style)

Priority: P1 (HIGH)

Author a typed JSON spec, then render. Never hand-place pixels in prose, and never ship Mermaid as the deliverable.

Pick One Type

Type Use for
architecture Components, services, cloud and trust boundaries
workflow Processes, approval gates, runbooks, CI/CD
sequence Call chains, request lifecycles, async traces
dataflow Pipelines, ETL, lineage, consumers
lifecycle State transitions, retries, terminal states

One type per diagram. A design doc usually needs architecture plus one of sequence or dataflow.

Render Path

  1. Check whether the Archify skill is installed (archify/SKILL.md under any agent skills directory).
  2. Installed: author the JSON against its schemas/<type>.schema.json, then run archify validate <type> <file>.json after every edit and archify deliver once at the end. A non-zero exit is never a success.
  3. Not installed: emit inline SVG directly, following the style contract. Same tokens, same geometry, same legend rules.
  4. Either way the spec is the source of truth: nodes carry id, type, label, optional sublabel and tag; edges carry from, to, label, variant; groups list the ids they wrap.

Semantics Are Colors

  • Node type is meaning, not decoration: frontend, backend, database, cloud, security, messagebus, external.
  • Edge variant is meaning: default plain call, emphasis main request path, security auth or policy hop, dashed async or event.
  • Never introduce a color outside that map, and never inline a literal hex that breaks dark/light parity.
  • Group frames come in two kinds only: region for deployment or ownership, security-group for a trust boundary.

Composition Rules

  • One left-to-right main path; side branches leave the nearest main-path node.
  • At most 12 primary nodes. Split the view before crowding it.
  • Number every lane or stage as 01 / Label, in order.
  • Every edge carries a label unless both endpoints already imply the protocol, direction, and sync behavior.
  • Spacing means clear gap, not center distance: leave more than the label mask width plus 8px.
  • Legend is mandatory and lists only the kinds actually present.

Read the full file on GitHub · 73 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 73 lines · 63 tokens per session scan A c5ab590434df

Subscribe to this mod's changes

system-design-diagramming is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 863 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json…

shadcn-ui/ui · 94 tokens

magic-ui

Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.

magicuidesign/magicui · 56 tokens

components

React component architecture for creating composable, accessible components with data attributes. Use when creating/updating composable components, not for higher-level feature/page components.

udecode/plate-playground-template · 33 tokens

multi-surface-render

Multi-surface rendering with json-render — one JSON spec produces React web, Next.js, React Native, Ink terminal UIs, PDFs, emails, Remotion videos, OG images, and 3D scenes. Covers renderer target selection, registry mapping, and platform APIs (renderToBuffer, renderToStream, renderToFile). Use when generating output…

yonatangross/orchestkit · 98 tokens

ui-beats

Use this skill when users want to add, customize, or troubleshoot UI Beats components in React/Next.js projects. It covers component selection, shadcn registry installation from uibeats.com, the UI Beats MCP server, motion and reduced-motion handling, and integration patterns for animated sections.

nikhils4/ui-beats · 62 tokens

nextjs-shadcn

Creates Next.js frontends with shadcn/ui. Use when building React UIs, components, pages, or applications with shadcn, Tailwind, or modern frontend patterns. Also use when the user asks to create a new Next.js project, add UI components, style pages, or build any web interface — even if they don't mention shadcn…

laguagu/claude-code-nextjs-skills · 80 tokens