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/nomarj/sigil/interactive-dashboard-buildernpx skills add NOMARJ/sigil --skill interactive-dashboard-buildergit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/interactive-dashboard-builder)<a href="https://agentmods.dev/skills/nomarj/sigil/interactive-dashboard-builder"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/interactive-dashboard-builder.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.00058 | $0.00908 |
| Opus 5 | $0.00029 | $0.00454 |
| Sonnet 5 | $0.00012 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
interactive-dashboard-builder 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 2d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Dashboard Builder
Build standalone HTML dashboards that work in any browser — no server, no dependencies beyond CDN-hosted Chart.js.
When to Use
- User has data (CSV, JSON, SQL results, spreadsheet) and wants a visual overview
- Need a shareable report that works offline
- Quick dashboard without setting up Metabase/Grafana/Tableau
- Prototype before building a production dashboard
Architecture
Single .html file containing:
- Chart.js (via CDN) for all visualizations
- Inline CSS for professional styling (dark/light theme support)
- Vanilla JS for interactivity (filters, tooltips, responsive layout)
- Embedded data as JSON within the file (no external API calls)
Build Process
Step 1: Understand the Data
- Read the data source (CSV, JSON, database results)
- Profile: row count, column types, date ranges, categorical values
- Identify the key dimensions (what to filter/group by) and measures (what to chart)
Step 2: Design the Layout
Standard dashboard layout:
┌─────────────────────────────────────────────────┐
│ Dashboard Title [Filters ▾] │
├──────────┬──────────┬──────────┬────────────────┤
│ KPI 1 │ KPI 2 │ KPI 3 │ KPI 4 │
├──────────┴──────────┴──────────┴────────────────┤
│ │
│ Primary Chart (line/bar/area) │
│ │
├─────────────────────┬────────────────────────────┤
│ Secondary Chart │ Secondary Chart │
│ (pie/donut) │ (bar/comparison) │
├─────────────────────┴────────────────────────────┤
│ Data Table │
└──────────────────────────────────────────────────┘
Step 3: Chart Type Selection
| Data Pattern | Recommended Chart | Chart.js Type |
|---|---|---|
| Trend over time | Line chart | line |
| Category comparison | Horizontal bar | bar (indexAxis: 'y') |
| Part of whole | Donut chart | doughnut |
| Distribution | Histogram (bar) | bar |
| Two variables | Scatter plot | scatter |
| Multiple series | Stacked bar or grouped bar | bar (stacked) |
| KPI / single number | Big number card | HTML/CSS |
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.
- 2d ago First seen · 111 lines · 58 tokens per session scan A 3e86f3733be5
interactive-dashboard-builder is a skill published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 908 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-09-03.
Other skills, from other repositories
web-ui-review
Frontend code quality checklist and review automation scripts for PRs touching UI, components, styles, and browser interactions.
qa-design
UI/UX design audit and verification of web best practices, including responsive/mobile-first breakpoints. Trigger when the user wants to audit the design, verify the UI/UX, check responsive behaviour, or improve the user interface.
dev-frontend-design
Distinctive UI design with strong art direction. Trigger when the user wants to create an interface, a landing page, a visual component, or when frontend code creation is detected without a defined design direction.
dev-shadcn
Integration and customization of shadcn/ui (copy-paste React components, Radix + Tailwind). Trigger when the user wants to install shadcn, add components, customize the theme, or when shadcn/ui usage is detected in the project.
craft
Create distinctive, production-grade frontend interfaces with high design quality. Auto-stacked onto an implementation path when a task involves frontend/UI work — pages, components, layouts, styles, interactions. Also available on demand as tn:craft.
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.