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 sigistry/marketplace --skill architecture-diagramminggit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/architecture-diagramming)<a href="https://agentmods.dev/skills/sigistry/marketplace/architecture-diagramming"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/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/sigistry/marketplace/architecture-diagramming"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/architecture-diagramming.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.00073 | $0.00652 |
| Opus 5 | $0.00036 | $0.00326 |
| Sonnet 5 | $0.00015 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Diagramming
Purpose
Provide standardized methodology and templates for generating architecture diagrams from codebase analysis. Uses the C4 Model for hierarchical architecture views and Mermaid for diagram rendering.
C4 Model Overview
The C4 Model defines four levels of architecture abstraction:
| Level | Name | Shows | When to Use |
|---|---|---|---|
| 1 | System Context | System + external actors | Always, the "big picture" |
| 2 | Container | Applications, data stores, services | When multiple deployable units exist |
| 3 | Component | Internal modules within a container | When analyzing a specific service |
| 4 | Code | Classes, interfaces | Rarely, only for critical components |
Diagram Selection Guide
Choose diagrams based on what exists in the codebase:
| What You Find | Diagrams to Generate |
|---|---|
| Multiple services/microservices | System Overview (L1), Container (L2), Dependency Graph |
| Database schemas/models | ER Diagram |
| API endpoints | API Interaction Diagram |
| Message queues/events | Event Flow Diagram |
| Multi-step workflows | Sequence Diagrams |
| Docker/K8s configs | Deployment/Infrastructure Diagram |
| Monolith with modules | Component Diagram (L3) |
Diagram Generation Process
- Scan project structure to identify components and boundaries
- Read config files (docker-compose, k8s, CI/CD, infrastructure-as-code)
- Map entry points, routes, and service communication
- Identify data stores and their relationships
- Select appropriate diagram types from the guide above
- Generate only diagrams relevant to findings, do not include generic templates
- Use proper Mermaid syntax with styling (subgraphs, colors, labels)
Mermaid Styling Conventions
%% Color coding for diagram elements:
%% - External actors/users: fill:#e1f5fe (light blue)
%% - External services: fill:#ffebee (light red)
%% - Core services: default styling
%% - Databases: use cylinder notation [( )]
%% - Critical components: fill:#fff3e0 (light orange)
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.
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.
- 11d ago First seen · 71 lines · 73 tokens per session scan A 32333d96ee74
architecture-diagramming is a skill published in the GitHub repository sigistry/marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 652 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
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…
steve-jobs-design-review
Review designs, products, and features with Steve Jobs' standards: ruthless simplicity, focus, and end-to-end excellence. Use when the user mentions "Steve Jobs review", "design review", "product review", "what would Steve do", "insanely great", "this feels too complicated", "too many features", "product taste"…
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", "typographic scale", or "the text is hard to read". Also trigger when choosing between system…
hooked-ux
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building…