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.
npx skills add sananthanarayan/skilldrop --skill architecture-diagramsgit clone --depth 1 https://github.com/sananthanarayan/skilldropWrote 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.
[](https://agentmods.dev/skills/sananthanarayan/skilldrop/architecture-diagrams)<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.
<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>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.00072 | $0.01056 |
| Opus 5 | $0.00036 | $0.00528 |
| Sonnet 5 | $0.00014 | $0.00211 |
| Haiku 4.5 | $0.00007 | $0.00106 |
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.
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
-
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.
-
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 flowchartorgraphRequest flow across services / call order matters Mermaid sequenceDiagramStrategic / multi-level view (context → container → component) C4 (PlantUML !include c4) Data model, tables, relationships Mermaid erDiagramState machine / workflow Mermaid stateDiagram-v2Class / type hierarchy Mermaid classDiagramLooks-pretty UML-style for slides PlantUML -
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. -
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-diagramsskill)".
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.
templates/mermaid-flowchart.md— basic boxes-and-arrows startertemplates/mermaid-sequence.md— sequenceDiagram with actors and async messagestemplates/mermaid-aws.md— AWS-flavoured flowchart using emojis as service iconstemplates/c4-container.puml— C4 container diagram skeleton (PlantUML)
What ships with it
10 files 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.
- evals/eval_queries.json 766 B
- evals/evals.json 784 B
- examples/aws-three-tier.md 1.7 KB
- examples/c4-container-saas.md 2.3 KB
- examples/microservices-sequence.md 1.7 KB
- manifest.json 799 B
- templates/c4-container.puml 1.2 KB
- templates/mermaid-aws.md 1.7 KB
- templates/mermaid-flowchart.md 1014 B
- templates/mermaid-sequence.md 1.2 KB
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.
- 10d ago First seen · 67 lines · 72 tokens per session scan A 835ed396d1c3
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.
Other skills, from other repositories
options
Present multiple design options as a vertical stack of anchored turns.
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.
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.
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…
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.
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…