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 AgenticAIPlan/AgenticAISkills --skill frontend-diagram-systemgit clone --depth 1 https://github.com/AgenticAIPlan/AgenticAISkillsWrote 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/agenticaiplan/agenticaiskills/frontend-diagram-system)<a href="https://agentmods.dev/skills/agenticaiplan/agenticaiskills/frontend-diagram-system"><img src="https://agentmods.dev/badge/skills/agenticaiplan/agenticaiskills/frontend-diagram-system/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/agenticaiplan/agenticaiskills/frontend-diagram-system"><img src="https://agentmods.dev/badge/skills/agenticaiplan/agenticaiskills/frontend-diagram-system.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.00141 | $0.02694 |
| Opus 5 | $0.00071 | $0.01347 |
| Sonnet 5 | $0.00028 | $0.00539 |
| Haiku 4.5 | $0.00014 | $0.00269 |
Grade A, and why
frontend-diagram-system 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 — 527 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Diagram System
This skill turns a static technical document into a frontend-based diagram system that is:
- visually polished enough for formal proposal decks and client demos
- structured enough to explain complex technical ideas clearly
- interactive enough for live walkthroughs
- exportable enough for Word, PPT, and PDF deliverables
What this skill is for
Use this skill when the user needs a diagram workflow that combines:
- technical accuracy
- presentation-grade visual design
- frontend interaction
- export-friendly output
This is not generic infographic generation.
This skill is specifically for cases where diagrams need to live in a frontend page first, then be refined, reviewed, and exported.
Typical requests that should trigger this skill:
- "把方案内容做成一个可演示页面"
- "做一套可导出的技术方案图"
- "除了 Word，我还想现场给客户演示页面版"
- "把架构图做得可以 hover / click 讲解"
- "同一套内容做成 Apple / Palantir / Mission Control 三种风格"
- "把技术方案图做成可导出 PNG 的前端系统"
Core principle
Treat diagrams as a product system, not single images.
That means every diagram should have:
- a clear semantic job
- a reusable visual grammar
- a presentation mode
- an export mode
- optional detail expansion for live explanation
Workflow
Follow this sequence.
1. Normalize the content
Before drawing anything, reduce the source material into diagram-ready units.
For each target diagram, define:
- title
- one sentence purpose
- diagram type: overview, layer stack, pipeline, topology, factor map, milestone, decision tree, ecosystem map
- 3-7 primary entities
- 1 dominant relationship type
- optional secondary detail lists for click/hover expansion
If a diagram tries to explain more than one central relationship, split it.
Bad:
- one figure mixing stakeholders, technical layers, timeline, and outputs
Good:
- one stakeholder coordination diagram
- one three-layer capability diagram
- one data-to-decision pipeline
2. Define the design system first
Do not start by drawing cards.
Define a visual system before implementing diagrams:
What ships with it
3 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.
- 11d ago First seen · 527 lines · 141 tokens per session scan A 30d1bf65e55d
frontend-diagram-system is a skill published in the GitHub repository AgenticAIPlan/AgenticAISkills (11 stars, last pushed 3mo ago), licensed MIT. It adds 141 tokens to every session and 2,694 once invoked, about $0.0007 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-30.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…