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 anton-abyzov/specweave --skill diagramsgit clone --depth 1 https://github.com/anton-abyzov/specweaveWrote 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/anton-abyzov/specweave/diagrams)<a href="https://agentmods.dev/skills/anton-abyzov/specweave/diagrams"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/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/anton-abyzov/specweave/diagrams"><img src="https://agentmods.dev/badge/skills/anton-abyzov/specweave/diagrams.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.00000 | $0.05484 |
| Opus 5 | $0.00000 | $0.02742 |
| Sonnet 5 | $0.00000 | $0.01097 |
| Haiku 4.5 | $0.00000 | $0.00548 |
Grade A, and why
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 8d 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 — 747 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagrams Skill
You are an expert in creating Mermaid diagrams for SpecWeave projects, following C4 Model conventions and industry best practices. You handle the full lifecycle: detecting diagram type, loading context, generating diagrams, saving to correct locations, and validating rendering.
Required Reading (LOAD FIRST)
CRITICAL: Before creating ANY diagrams, read this guide:
This guide contains:
- C4 Model levels (Context, Container, Component, Code)
- Mermaid syntax rules (C4 diagrams start WITHOUT
mermaidkeyword!) - Diagram placement conventions
- Validation requirements (MUST verify rendering)
- SVG generation for production
Load this guide using the Read tool BEFORE creating diagrams.
Core Responsibilities
- Detect diagram type from user requests
- Load context from specs and architecture docs when available
- Create C4 architecture diagrams (Context, Container, Component, Code)
- Generate sequence diagrams from API flows and use cases
- Design ER diagrams from data models
- Create deployment diagrams from infrastructure docs
- Update diagrams when architecture changes
- Validate syntax and conventions
- Place diagrams in correct locations (HLD vs LLD, architecture vs operations)
- Ensure diagrams render correctly - Validate before saving
Activation Keywords
This skill activates when user mentions:
- General: "create diagram", "draw diagram", "visualize", "generate diagram"
- C4 Model: "C4 diagram", "context diagram", "container diagram", "component diagram"
- Flows: "sequence diagram", "flow diagram", "interaction diagram"
- Data: "ER diagram", "entity relationship", "data model", "database schema"
- Infrastructure: "deployment diagram", "architecture diagram", "infrastructure diagram"
Workflow
Step 1: Detect Diagram Type
Analyze user's request to determine:
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.
- 8d ago First seen · 747 lines · 0 tokens per session scan A 45eadf864f2a
diagrams is a skill published in the GitHub repository anton-abyzov/specweave (160 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,484 tokens. 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
preview-design
Render a real artifact through this branch's local MERIDIAN design code (not the published npm package) so the team can test the new Design Convention on the document / handoff / platform surfaces before it ships. Use for /preview-design, "preview the design convention", "render this with the new design", or Design…
atomic-visual-options
Planning-phase visual comparison aid. Renders 2-4 side-by-side variants per decision dimension as a single throwaway, self-contained HTML file and captures the user's pick as typed terminal codes (e.g. "A2 B3"). Auto-fires on phrases like "show me a few options", "mock up some variants", "let me see this side by…
accessibility
This skill should be used when the user asks to "add accessibility", "check ARIA", "handle keyboard navigation", "add focus management", or creates UI components, forms, or interactive elements. Provides WCAG 2.2 AA patterns for keyboard navigation, ARIA roles and states, focus management, color contrast, and screen…
ui-design
This skill should be used when the user asks to "design a component", "pick colors", "improve typography", "fix spacing", "choose a layout", or discusses visual design, CSS, styling decisions, or responsive interfaces. Provides patterns for typography scales, color systems, spacing, and production-grade UI design.
generating-diagrams
Use when generating flowcharts, diagrams, dependency graphs, or visual representations of processes, relationships, architecture, or state machines. Triggers: 'diagram this', 'flowchart', 'visualize', 'dependency graph', 'ER diagram', 'state machine diagram', 'class diagram', 'sequence diagram', 'map the…
mermaid-diagrams
Author Mermaid diagrams for architecture work — C4 context/container/component, sequence, deployment, flowchart, and state diagrams with copy-paste examples and CLI validation. Use when the user wants a text-based diagram, a diagram embedded in Markdown, or a quick architecture sketch.