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 HK-hub/AgentSkills --skill figma-generate-diagramgit clone --depth 1 https://github.com/HK-hub/AgentSkillsWrote 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/hk-hub/agentskills/figma-generate-diagram)<a href="https://agentmods.dev/skills/hk-hub/agentskills/figma-generate-diagram"><img src="https://agentmods.dev/badge/skills/hk-hub/agentskills/figma-generate-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/hk-hub/agentskills/figma-generate-diagram"><img src="https://agentmods.dev/badge/skills/hk-hub/agentskills/figma-generate-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.00164 | $0.02340 |
| Opus 5 | $0.00082 | $0.01170 |
| Sonnet 5 | $0.00033 | $0.00468 |
| Haiku 4.5 | $0.00016 | $0.00234 |
Grade A, and why
figma-generate-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 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.
This is a copy
86% identical to figma-generate-diagram — 54 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
generate-diagram
You MUST load this skill before every generate_diagram tool call. Skipping it causes preventable rendering failures and low-quality output.
generate_diagram takes Mermaid.js syntax and produces an editable FigJam diagram. This skill routes you to the right per-type guidance and sets universal constraints.
Step 1: Is generate_diagram the right tool?
Supported diagram types
flowchart, sequenceDiagram, stateDiagram / stateDiagram-v2, gantt, erDiagram.
Unsupported — don't call the tool
If the user wants any of these, tell them directly that generate_diagram doesn't support it instead of calling the tool and failing:
- Pie chart, mindmap, venn diagram, class diagram, journey, timeline, quadrant, C4, git graph, requirement diagram
When to push the user to edit in Figma
The tool cannot:
- Change fonts on an existing diagram
- Move individual shapes
- Edit a diagram node-by-node after generation
If the user asks for any of those on an existing diagram, recommend they open the diagram in Figma and edit there. For content-level changes, it's usually faster to regenerate.
Step 2: Pick the diagram type
Lightweight routing — use the first match.
| User wants… | Type | Next step |
|---|---|---|
| Services + datastores + queues + integrations | Architecture flowchart | Read references/architecture.md |
| Decision tree, process flow, pipeline, dependency graph, user journey | Flowchart | Read references/flowchart.md |
| Interactions between parties over time (API calls, auth, messaging) | Sequence diagram | Read references/sequence.md |
| Data model, tables, keys, cardinality | ER diagram | Read references/erd.md |
| Named states with transitions between them | State diagram | Read references/state.md |
| Project schedule with dates, milestones | Gantt chart | Read references/gantt.md |
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.
- 8d ago First seen · 113 lines · 164 tokens per session scan A 7297638dbf21
figma-generate-diagram is a skill published in the GitHub repository HK-hub/AgentSkills (6 stars, last pushed 25d ago), licensed MIT. It adds 164 tokens to every session and 2,340 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to figma-generate-diagram, differing in 54 lines, and is treated as a copy.
Other skills, from other repositories
mermaid
Create, validate, and repair Mermaid.js diagrams. Use when generating flowcharts, sequence, class, ER, state, or Gantt diagrams, or any visualization.
loft
Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks.…
plannotator-annotate
Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces with screenshot evidence and a verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right.
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
layout-skill
Layer A layout-mechanics reference. Stacks on any style skill when the screen is an app shell, dashboard, settings, list-detail, mail/inbox, or any layout with fixed regions plus a scrolling body — or when a layout breaks under long, empty, or unbroken content. Owns spatial structure and scroll ownership; owns zero…