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 d-oit/rust-2026-template --skill architecture-diagramgit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote 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/d-oit/rust-2026-template/architecture-diagram)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/architecture-diagram"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/architecture-diagram.svg" alt="Measured on agentmods" 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.00067 | $0.00702 |
| Opus 5 | $0.00034 | $0.00351 |
| Sonnet 5 | $0.00013 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
overview-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 7d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview Diagram
Generates a human-friendly overview infographic showing what the project is, how to get started, what's inside, and how it all connects.
When to Use
- User asks to update / regenerate / sync the overview diagram.
- Crates, skills, scripts, or workflows have changed.
- First-time setup (diagram doesn't exist yet).
Execution
Step 1 — Locate Project Root
ls .agents/ Cargo.toml 2>/dev/null || echo "NOT_FOUND"
Step 2 — Generate the Diagram
python .agents/skills/architecture-diagram/scripts/generate_overview.py \
--root . \
--out .template/overview.excalidraw \
--svg-out .template/overview.svg
The script auto-discovers at runtime:
- Workspace crates →
cargo metadata(with Cargo.toml glob fallback) - AI skills →
.agents/skills/*/directories - Commands →
.opencode/commands/*.md
Step 3 — Sync to Docs
cp .template/overview.svg docs/src/overview.svg
Step 4 — Confirm and Report
After the script exits:
- Tell the user the output path.
- Report counts: N crates · M skills.
- If counts differ from the last known state, summarize what changed.
Output
.template/overview.excalidraw— editable Excalidraw source.template/overview.svg— generated SVG for docs embedding
Optional Dependencies
Node.js (for SVG export)
Required for SVG/PNG export from Excalidraw:
npm ci
Without Node.js, use --no-export to generate only the .excalidraw source.
CLI Flags
| Flag | Description |
|---|---|
--root PATH |
Workspace root (default: .) |
--out PATH |
Excalidraw output path (default: .template/overview.excalidraw) |
--svg-out PATH |
SVG export path (default: .template/overview.svg) |
--png-out PATH |
PNG export path (optional) |
--no-export |
Skip SVG/PNG export (Excalidraw only) |
Rationalizations
| Rationalization | Reality |
|---|---|
| "The overview is close enough, no need to regenerate" | Stale diagrams mislead new contributors about project structure. |
| "I'll update the diagram manually" | Manual edits break on next regeneration and introduce inconsistencies. |
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.
- 7d ago First seen · 96 lines · 67 tokens per session scan A 07ee0b138a48
overview-diagram is a skill published in the GitHub repository d-oit/rust-2026-template (10 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 702 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-08-31.
Other skills, from other repositories
blockwatch
Use when writing or modifying code in a project that uses BlockWatch — proactively link co-dependent code with / so it catches drift when one side changes without the other (an enum and its docs, a constant and its config), or assert two places hold the same value with . Also for lists that must stay sorted/unique or…
visual-assets-generation
Generate visual assets (ASCII art, diagrams, banners) for repos and documentation.
public-repo-creation
Create production-ready public GitHub repositories with comprehensive documentation, automated setup, and quality assurance.
dear-agent
A procedure for following this workspace’s documentation rules, including its required project files and single handoff document. A handoff records what was done, what comes next, and what is blocked.
publish-rust
Verify and release a Rust crate or workspace. Bumps version, commits, tags, pushes. CI-driven by default; --local publishes directly.
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.