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 uthumany/uthy-legacy-os --skill dashboard-designgit clone --depth 1 https://github.com/uthumany/uthy-legacy-osWrote 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/uthumany/uthy-legacy-os/dashboard-design)<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/dashboard-design"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/dashboard-design/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/uthumany/uthy-legacy-os/dashboard-design"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/dashboard-design.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.00026 | $0.00927 |
| Opus 5.5 | $0.00010 | $0.00371 |
| Sonnet 5.5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
dashboard-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 2mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Design
Overview
A good dashboard answers questions. A great dashboard drives decisions. This skill covers dashboard design principles — choosing the right metrics, visualizing data effectively, and building dashboards that teams actually use.
When to Use
- Building a new dashboard for your product
- Redesigning a dashboard that nobody looks at
- Creating executive reports or weekly metric reviews
- Onboarding a team to data-driven decision-making
- Don't use for: ad-hoc analysis (use notebooks or query tools), operational monitoring (use alerting tools, not dashboards)
Instructions
1. Define the Audience and Purpose
Every dashboard needs ONE clear purpose:
- Execution dashboard: For the team making daily decisions. Real-time or daily.
- Health dashboard: For managers tracking trends. Weekly or monthly.
- Strategic dashboard: For executives overseeing goals. Monthly or quarterly.
2. Choose the Right Metrics
- Actionable → If this metric moves, can someone take action?
- Leading → Predicts future outcomes (not lagging/too late)
- Specific → Clear definition, unambiguous
- Few → 5-9 metrics max per dashboard. More = noise
3. Design the Hierarchy
┌─────────────────────────────────────┐
│ NORTH STAR (top, prominent) │
│ One number that captures value │
├────────┬────────┬────────┬─────────┤
│ Input │ Input │ Input │ Input │
│ Metric │ Metric │ Metric │ Metric │
│ 1 │ 2 │ 3 │ 4 │
├────────┴────────┴────────┴─────────┤
│ Segments / Breakdowns │
│ (platform, plan, cohort, etc.) │
└─────────────────────────────────────┘
4. Visualization Best Practices
- Line charts for trends over time (most common, most useful)
- Bar charts for comparisons between groups
- Single number + sparkline for the North Star metric
- Heatmap for density or cohort analysis
- Table for detailed data (use sparingly)
- ❌ Pie charts (hard to compare), gauges (take too much space), 3D charts (distorting)
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.
- 2mo ago First seen · 103 lines · 26 tokens per session scan A 8eb0b17bb557
dashboard-design is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 927 once invoked, about $0.0001 per session on Opus 5.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.
dashboard-design compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dashboard-designuthumany/uthy-legacy-os | Skill | 5 | 5mo ago | MIT | A | 26 | Claude Code, Codex |
| webgl-holographic-foilnexu-io/open-design | Skill | 106k | today | Apache-2.0 | A | 41 | Claude Code, Codex |
| html-ppt-hermes-cyber-terminalnexu-io/open-design | Skill | 106k | today | Apache-2.0 | A | 53 | Claude Code, Codex |
| html-ppt-taste-brutalistnexu-io/open-design | Skill | 106k | today | Apache-2.0 | A | 78 | Claude Code, Codex |
| visual-ralphYeachan-Heo/oh-my-codex | Skill | 34k | today | MIT | A | 52 | Codex |
| glance-canonical-layoutsandroid/skills | Skill | 10k | 2d ago | Apache-2.0 | A | 56 | Claude Code |
| accessibilitymicrosoft/hve-core | Skill | 1.6k | today | MIT | A | 47 | Claude Code |