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 mgiovani/cc-arsenal --skill docs-diagramgit clone --depth 1 https://github.com/mgiovani/cc-arsenalWrote 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/mgiovani/cc-arsenal/docs-diagram)<a href="https://agentmods.dev/skills/mgiovani/cc-arsenal/docs-diagram"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/docs-diagram/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/mgiovani/cc-arsenal/docs-diagram"><img src="https://agentmods.dev/badge/skills/mgiovani/cc-arsenal/docs-diagram.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.00118 | $0.01349 |
| Opus 5 | $0.00059 | $0.00674 |
| Sonnet 5 | $0.00024 | $0.00270 |
| Haiku 4.5 | $0.00012 | $0.00135 |
Grade A, and why
docs-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 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate System Diagrams
Generate a Mermaid diagram (ER, architecture, deployment, or security) from the
real codebase and write it to docs/.
Supported Diagram Types
| Type | Output File | Description |
|---|---|---|
er |
docs/data-model.md |
Entity-Relationship diagram from database models |
arch |
docs/architecture.md |
System architecture and component relationships |
deployment |
docs/deployment.md |
Deployment infrastructure and CI/CD |
security |
docs/security.md |
Security architecture and data flow |
Workflow
1. Parse the request
Extract the diagram type (er, arch, deployment, security) and any optional
scope context (e.g. "for the user and order tables"). If the type is missing or
invalid, don't guess: stop, and end your response with a direct question naming
the supported types, e.g. "Which diagram type do you want: architecture, er,
deployment, or security?". Listing the types without asking, or asking without
listing them, is not enough. Go no further until the user answers.
2. Analyze the codebase
- Scoped request (e.g. "er diagram for the user and order tables"): Read/Grep the named files directly.
- Broad or ambiguous request (e.g. "show me the architecture" on an unfamiliar
codebase): when a Task tool is available, spawn one Explore subagent per aspect
that matters for the diagram type (e.g. for
arch: services, databases, external integrations, data flow). Without a Task tool, run the same per-aspect checks sequentially inline with Read/Grep/Glob instead: same checks, no parallelism, just slower.
See references/detection-patterns.md for detection commands per diagram type.
3. Verify before adding anything
Diagrams must represent real, existing components, never a plausible guess.
- Read the file that defines a component before adding it; don't add it from memory or inference.
- Confirm a relationship by finding the actual import/reference/FK in code, not by assuming two similarly-named things are connected.
- Get counts by running a command (e.g.
find . -name "*service*" | wc -l), then use that number, never estimate "about 5 services". - Drop anything that can't be verified this way. An empty directory or an unused stub file is not a component.
What ships with it
8 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 · 127 lines · 118 tokens per session scan A be1b2fc9517a
docs-diagram is a skill published in the GitHub repository mgiovani/cc-arsenal (8 stars, last pushed 9d ago), licensed MIT. It adds 118 tokens to every session and 1,349 once invoked, about $0.0006 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
cli-anything-photoshop
A command-line tool that controls Adobe Photoshop through Windows automation. It can work with Photoshop documents, layers, selections, text, image adjustments, and exports.
extract-design-system
Extract design primitives from a public website and generate starter token files for your project.
double-diamond
A four-stage design method for understanding a problem, defining it clearly, exploring possible solutions, and choosing one to deliver.
nous-branding
Generate images and content consistent with the Nous Research brand identity. Use when creating visuals in the Nous / Theia / Hermes ecosystem: a "cyber-classical" style blending neo-classical statuary, cyberpunk/industrial grunge, and retro anime illustration. Covers official brand color palette, typography…
figma-use
Control Figma via CLI — create shapes, frames, text, components, set styles, layout, variables, export images. Use when asked to create/modify Figma designs or automate design tasks.
awesome-design-md
Create a DESIGN.md style baseline BEFORE building UI. Use FIRST when no design draft exists — installs a proven visual style, then invoke frontend-design to implement. For borrowing a known product style, getting consistent typography/colors/spacing, or needing a fast visual starting point.