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 nimrodfisher/data-analytics-skills --skill dashboard-specificationgit clone --depth 1 https://github.com/nimrodfisher/data-analytics-skillsWrote 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/nimrodfisher/data-analytics-skills/dashboard-specification)<a href="https://agentmods.dev/skills/nimrodfisher/data-analytics-skills/dashboard-specification"><img src="https://agentmods.dev/badge/skills/nimrodfisher/data-analytics-skills/dashboard-specification/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/nimrodfisher/data-analytics-skills/dashboard-specification"><img src="https://agentmods.dev/badge/skills/nimrodfisher/data-analytics-skills/dashboard-specification.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.00028 | $0.00592 |
| Opus 5.5 | $0.00011 | $0.00237 |
| Sonnet 5.5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
dashboard-specification 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dashboard Specification
When to use
- A new dashboard is being built and developers need a clear brief before starting
- An existing dashboard is confusing or underused and needs a structured redesign
- Stakeholders and the data team have different ideas about what a dashboard should show
- Documenting dashboard requirements as part of a broader data product process
- Creating a self-service analytics specification that can be handed off without multiple Q&A rounds
Process
- Define the purpose — write one sentence: "This dashboard answers [question] for [audience] who need to [decision or action]." If it can't be stated in one sentence, the scope needs narrowing first. See
references/dashboard_design_principles.md. - Profile target users — for each audience (executive, manager, IC), document their visit frequency, the primary question they come to answer, and their technical comfort level. Users with different needs usually need different dashboards, not more filters on one.
- Define the metric hierarchy — list primary KPIs (hero numbers at the top), secondary supporting metrics, and detail-level breakdowns. A dashboard with more than 10–12 distinct metrics is trying to do too much.
- Design the information architecture — sketch the layout using the hero → trends → breakdowns → details pattern. Position the most important information in the top-left. Use
references/dashboard_requirements_guide.mdfor layout patterns. - Specify interactivity — list global filters (date range, region, segment), drill-down paths, click actions, and hover tooltip content. Every filter and drill-down adds complexity; justify each one.
- Document data requirements and success criteria — for each metric, record the source table, transformation logic, and refresh frequency. Define how dashboard success will be measured (adoption rate, reduction in ad-hoc requests). Complete
assets/dashboard_spec_template.md.
Inputs the skill needs
- The business question the dashboard is meant to answer
- A list of candidate metrics (team can provide a rough list; you'll curate it)
- The primary audience (role, visit frequency, decision they make)
- Data availability: confirmed source tables and refresh schedules
- Any constraints: tool (Tableau, Looker, Metabase, etc.), branding guidelines
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.
- 2mo ago First seen · 34 lines · 28 tokens per session scan A ce1494b3d48c
dashboard-specification is a skill published in the GitHub repository nimrodfisher/data-analytics-skills (518 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 592 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-30.
dashboard-specification compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dashboard-specificationnimrodfisher/data-analytics-skills | Skill | 518 | 1mo ago | MIT | A | 28 | Claude Code, Codex |
| frontend-designanthropics/claude-plugins-official | Skill | 46k | yesterday | Apache-2.0 | A | 40 | Claude Code |
| display-glasses-with-jetpack-compose-glimmerandroid/skills | Skill | 10k | yesterday | Apache-2.0 | A | 112 | Claude Code |
| glance-canonical-layoutsandroid/skills | Skill | 10k | yesterday | Apache-2.0 | A | 56 | Claude Code |
| readtw93/Waza | Skill | 7.5k | 5d ago | MIT | A | 61 | Claude Code |
| visual-editBuilderIO/skills | Skill | 4.6k | 4d ago | MIT | A | 42 | Claude Code |
| visual-planBuilderIO/skills | Skill | 4.6k | 4d ago | MIT | A | 32 | Claude Code |