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 agentmods add skills/baokhang83/fluencyloop/diagram-designnpx skills add baokhang83/fluencyloop --skill diagram-designgit clone --depth 1 https://github.com/baokhang83/fluencyloopWrote 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/baokhang83/fluencyloop/diagram-design)<a href="https://agentmods.dev/skills/baokhang83/fluencyloop/diagram-design"><img src="https://agentmods.dev/badge/skills/baokhang83/fluencyloop/diagram-design.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 | $0.00061 | $0.02046 |
| Opus 5 | $0.00030 | $0.01023 |
| Sonnet 5 | $0.00012 | $0.00409 |
| Haiku 4.5 | $0.00006 | $0.00205 |
Grade A, and why
diagram-design 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 4d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagram Design
Create one self-contained HTML file with inline SVG and CSS. Use a diagram only when it explains a relationship, flow, or structure better than prose or a table.
FluencyLoop embedded diagram fast path
Use this path when FluencyLoop asks for either
docs/fluencyloop/diagrams/product-overview.html or a file under
docs/fluencyloop/diagrams/records/. For a product overview, its prose is always
docs/fluencyloop/distillations/product.md; its companion is always
docs/fluencyloop/diagrams/product-overview.html. Never write docs/fluencyloop/product.md.
It is a focused companion inside FluencyLoop's local site, not a branded design-system deliverable.
FluencyLoop owns the surrounding site design, but the diagram must still describe the product
faithfully. Use a self-contained HTML document with inline SVG and CSS: no scripts, remote URLs,
remote fonts, iframes, or embedded executable content. Support the reader's themes with local
light tokens and a :root[data-fluencyloop-theme="dark"] token override.
Choose the rendering path by topology, not by the convenience of the renderer:
-
Use the native renderer only when one of its layouts faithfully captures every material node and relationship:
linearfor a 2–6 step path,hubfor a shared service/boundary with 2–7 direct participants,mergefor inputs or short chains that end at one result, orlayeredfor one-to-one adjacent-layer mappings. It supports 2–8 nodes and at most 10 edges. A graph with parallel flows that merge and then continue to another boundary does not fit these layouts; never recast the architecture merely to make the command pass. -
For a fitting native graph, run exactly one
fluencyloop diagramcommand. Give each node its short id, label, and detail as separate fields, then give the directed edges. For example:fluencyloop diagram --output docs/fluencyloop/diagrams/product-overview.html --layout hub \ --title "Dog selection" --hub selection \ --node list --label "Dog list" --detail "Chooses a dog" \ --node selection --label "Selection service" --detail "Owns selected dog" \ --node detail --label "Dog detail" --detail "Reads selected dog" \ --edge list selection --edge selection detail
What ships with it
60 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.
- assets/example-architecture-dark.html 11 KB
- assets/example-architecture-full.html 14 KB
- assets/example-architecture.html 12 KB
- assets/example-bar-dark.html 8.6 KB
- assets/example-bar-full.html 11 KB
- assets/example-bar.html 8.5 KB
- assets/example-data-flow-dark.html 13 KB
- assets/example-data-flow-full.html 15 KB
- assets/example-data-flow.html 12 KB
- assets/example-datalake-dark.html 24 KB
- assets/example-datalake-full.html 27 KB
- assets/example-datalake.html 26 KB
- assets/example-dp-integration-dark.html 14 KB
- assets/example-dp-integration-full.html 16 KB
- assets/example-dp-integration.html 14 KB
- assets/example-dp-security-matrix-dark.html 10.0 KB
- assets/example-dp-security-matrix-full.html 12 KB
- assets/example-dp-security-matrix.html 11 KB
- assets/example-er-dark.html 14 KB
- assets/example-er-full.html 16 KB
- assets/example-er.html 14 KB
- assets/example-flowchart-dark.html 8.7 KB
- assets/example-flowchart-full.html 12 KB
- assets/example-flowchart.html 8.7 KB
- assets/example-gantt-dark.html 9.8 KB
- assets/example-gantt-full.html 11 KB
- assets/example-gantt.html 9.5 KB
- assets/example-high-level-dark.html 23 KB
- assets/example-high-level-full.html 27 KB
- assets/example-high-level-vertical-dark.html 24 KB
- assets/example-high-level-vertical-full.html 27 KB
- assets/example-high-level-vertical.html 29 KB
- assets/example-high-level.html 26 KB
- assets/example-it-state-dark.html 12 KB
- assets/example-it-state-full.html 14 KB
- assets/example-it-state.html 12 KB
- assets/example-layers-dark.html 6.4 KB
- assets/example-layers-full.html 9.5 KB
- assets/example-layers.html 6.4 KB
- assets/example-line-dark.html 7.1 KB
- assets/example-line-full.html 9.5 KB
- assets/example-line.html 7.0 KB
- assets/example-loop-dark.html 6.6 KB
- assets/example-loop-full.html 9.7 KB
- assets/example-loop-terminal.html 9.7 KB
- assets/example-loop.html 6.6 KB
- assets/example-medallion-dark.html 13 KB
- assets/example-medallion-full.html 16 KB
- assets/example-medallion.html 13 KB
- assets/example-nested-dark.html 6.3 KB
- assets/example-nested-full.html 9.3 KB
- assets/example-nested.html 6.4 KB
- assets/example-org-chart-dark.html 11 KB
- assets/example-org-chart-full.html 12 KB
- assets/example-org-chart.html 11 KB
- assets/example-process-dark.html 14 KB
- assets/example-process-full.html 17 KB
- assets/example-process.html 14 KB
- assets/example-pyramid-dark.html 6.2 KB
- assets/example-pyramid-full.html 9.2 KB
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.
- 4d ago First seen · 129 lines · 61 tokens per session scan A b84f0eb52197
diagram-design is a skill published in the GitHub repository baokhang83/fluencyloop (44 stars, last pushed 19d ago), licensed Apache-2.0. It adds 61 tokens to every session and 2,046 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-30.
Other skills, from other repositories
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
ce-prototype
Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to build, not polishing a feature that already works, not…
ce-polish
Polish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.
accessibility-audit
Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or…
frontend-component-build
Build production-ready frontend components with accessible markup, sensible props, defined states, and tested behavior. Use this skill whenever the user wants to build a component from scratch, refactor an existing one, design a component API, or implement a UI element with proper states and accessibility. Triggers on…
design-it
Use when turning a requirement, spec, or feature brief into a single self-contained HTML design document in a fixed house style — one styled HTML page with a table-of-contents, architecture/sequence SVG diagrams, code/SQL/YAML blocks, callout boxes, an aligned-decisions (已对齐结论) panel, test cases, and a code index.…