architecture-diagram

A guide for creating one self-contained HTML file that shows how software components fit together in a dark-themed architecture diagram. The diagram uses inline SVG, a web format for drawing shapes and connections.

In plain words
What is it for?
Use it to document software architecture, including services, plugins, core contracts, developer interfaces, execution environments, and event or observation systems.
Why use it?
It provides consistent visual rules for showing system layers, component roles, and the relationships between them. The result can be opened directly in a browser without separate image or script files.

Skill for Claude CodeCodex

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/agentera/agently/architecture-diagram
Any agent
npx skills add AgentEra/Agently --skill architecture-diagram
Clone the repo
git clone --depth 1 https://github.com/AgentEra/Agently

Made for: Claude Code, Codex.

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 517 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.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.00517
Opus 5 $0.00023 $0.00259
Sonnet 5 $0.00009 $0.00103
Haiku 4.5 $0.00005 $0.00052

Measured yesterday against content hash c99afdcb1352, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

examples/skills_executor/skills/architecture-diagram/SKILL.md · 41 lines

What it actually says

Architecture Diagram

Produce ONE self-contained HTML document (embedded CSS + inline SVG, no JavaScript, no external images; Google Fonts link is allowed). It must render correctly when opened directly in a browser.

Visual design system

  • Background #020617 with a subtle 40px grid pattern.
  • Font: JetBrains Mono (monospace) via Google Fonts.
  • Component boxes: rounded rects (rx="6"), 1.5px stroke, semi-transparent fills. Colour components by role:
    • facade / developer surface: fill rgba(8,51,68,0.4), stroke #22d3ee
    • core contracts: fill rgba(6,78,59,0.4), stroke #34d399
    • plugins / providers: fill rgba(120,53,15,0.3), stroke #fbbf24
    • execution environment / capabilities: fill rgba(76,29,149,0.4), stroke #a78bfa
    • observation / event bus: fill rgba(251,146,60,0.3), stroke #fb923c
    • external / generic: fill rgba(30,41,59,0.5), stroke #94a3b8
  • Component name at 11px white bold; sublabel at 8-9px #94a3b8.
  • Arrows via an SVG marker arrowhead; draw connecting arrows before boxes so they sit behind them.

Layout rules

  • Lay the system out as labelled horizontal bands stacked top-to-bottom, one band per architectural layer, with each layer's components inside its band.
  • Keep ≥40px vertical gaps between stacked rows; never overlap boxes.
  • Add a short header (title + subtitle) and a small legend mapping each colour to a layer. Place the legend outside every band.

Output

Return the complete HTML document as a single string. Do not include commentary outside the HTML.

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. yesterday First seen · 41 lines · 47 tokens per session scan A c99afdcb1352

Subscribe to this mod's changes

architecture-diagram is a skill published in the GitHub repository AgentEra/Agently (1,644 stars, last pushed 3d ago), licensed Apache-2.0. It adds 47 tokens to every session and 517 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-30.

Related

Other skills, from other repositories