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.
git clone --depth 1 https://github.com/fakoli/fakoli-pluginsWrote 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/agents/fakoli/fakoli-plugins/diagram-architect)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/diagram-architect"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/diagram-architect.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.00030 | $0.00163 |
| Opus 5 | $0.00015 | $0.00081 |
| Sonnet 5 | $0.00006 | $0.00033 |
| Haiku 4.5 | $0.00003 | $0.00016 |
Grade A, and why
diagram-architect 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 today.
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.
What it actually says
Read ../skills/excalidraw/SKILL.md relative to this agent file and use its converter workflow. Match the diagram to the intended audience and decision. Use repository evidence for current architecture, mark proposed relationships clearly, and preserve existing scene content when editing.
Organize a clear reading direction, group related components, and use labeled connectors to explain behavior. Generate a compact skeleton, check converter failures, inspect the resulting scene when an editor is available, and return the absolute .excalidraw path with material limitations. This specialist is optional; simple diagrams can be created directly by the primary agent.
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.
- today Changed · -315 lines · -527 tokens per session 7e7ed0e96a48
- 7d ago First seen · 325 lines · 557 tokens per session scan A 3acf964d24b8
diagram-architect is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 163 once invoked, about $0.0002 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 agents, from other repositories
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
design-director
Orchestrates the full design workflow for a project — from assessing needs to producing a styleguide and coordinating asset creation. Use when the user needs end-to-end design direction for a new project, website redesign, or brand refresh. Coordinates with media-plugin for asset generation. Context: User starting a…
design-doc-pages
Produces all per-page specification files (pages/home.md, pages/about.md, etc.) — each bundling section architecture, layout composition, media specs, and animation specs for one page. Runs in Wave 2 after styleguide.md is available. Context: Orchestrator needs all page specs after styleguide is ready user: "Create…
variation-generator
Generates N alternative design documents from an existing base design — varies colors, typography, animation intensity, and spacing density while preserving page structure and content. Each variation gets its own design document that can be implemented independently. Context: User wants 3 visual alternatives of their…
design-doc-foundation
Produces the foundational design files — design-document.md (index), styleguide.md (aesthetic profile, fonts, colors, spacing), and css-architecture.md (Tailwind config, CSS tokens, global styles). These are the first files created and are dependencies for all other design agents. Context: Orchestrator needs…
design-doc-media
Produces the media-plan.md file — style prefix for visual consistency, shared media assets (logo, product images, OG image), and icon master list. Runs in Wave 2 after styleguide.md is available. Context: Orchestrator needs media planning after styleguide is ready user: "Create media plan. Styleguide at…