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 HoangNguyen0403/agent-skills-standard --skill common-architecture-diagramminggit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/common-architecture-diagramming)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-architecture-diagramming"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-architecture-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.
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-architecture-diagramming"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-architecture-diagramming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00062 | $0.00616 |
| Opus 5 | $0.00031 | $0.00308 |
| Sonnet 5 | $0.00012 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
common-architecture-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 9d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Diagramming Standard
Priority: P1 (HIGH)
Guidelines
- Use C4 Model: Context -> Container -> Component -> Code.
- Audience-Centric: Tailor abstraction (Execs vs. Devs).
- Select Type: Sequence (Protocol), ERD (Data), State (Lifecycle), Cloud (Infra). See Selection.
- Explicit Labels: Label every arrow (e.g., "Uses", "HTTPS").
- Consistent Notation: Cylinders=DB, Rectangles=Systems, Dashed=Async.
- Metadata: Title, Date, Version, Author.
- Legend Mandatory: Define all shapes/colors/styles.
- Direction:
graph LR(Flow) orgraph TD(Hierarchy). - Deployment: Map containers to infrastructure.
- Governance: CRITICAL: Review best-practices.md before starting.
Workflow
- Name audience and the decision the diagram must support.
- Pick one level: context for external actors, container for deployable systems, component for one container; never mix levels.
- Pick notation: sequence for a request protocol, ERD for data ownership, state for lifecycle, deployment for infrastructure.
- Draw only decision-relevant nodes; label every relationship with protocol or event.
- Add title, scope/date/version, legend, and one review question for the intended audience.
See implementation examples for C4 container diagram in Mermaid.
Anti-Patterns
- Mixed Levels: DB columns in System Context.
- Unlabeled Arrows: Ambiguous relations.
- Mystery Shapes: Undefined in Legend.
- Dead Ends: Unconnected nodes.
- Clutter: >20 nodes/diagram.
- Acronyms: Undefined abbreviations.
References
- For design-session deliverables,
system-design-diagrammingsupersedes Mermaid with the Archify typed-spec style. - Diagram Selection
- Cloud Architecture
- C4 Model Guide
- Checklist
- Best Practices
What ships with it
7 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.
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.
- 9d ago First seen · 62 lines · 62 tokens per session scan A 965f6529a328
common-architecture-diagramming is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (565 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 616 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-09-03.
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…
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.
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.
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…
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.
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…