agentmods.dev

metrics-dashboard

metrics-dashboard is a skill for Claude Code from yuusakuri/agent-skills. It costs 47 tokens per session (1,247 once invoked), scanned A, a copy of metrics-dashboard, MIT.

A plan for choosing and designing a product metrics dashboard: a screen that tracks important measurements over time.

In plain words
What is it for?
Use it to define key metrics, data sources, charts, and alert thresholds for product analytics or performance monitoring.
Why use it?
It helps teams agree on useful measures, where the data comes from, how to display it, and when a result needs attention.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

not rated 2repo 14d ago A scan 47 tokens copy · 100% MIT

Good fit Use it to define key metrics, data sources, charts, and alert thresholds for product analytics or performance monitoring.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yuusakuri/agent-skills/metrics-dashboard
View source ↗ yuusakuri/agent-skills
Install

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.

Any agent
npx skills add yuusakuri/agent-skills --skill metrics-dashboard
Clone the repo
git clone --depth 1 https://github.com/yuusakuri/agent-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for metrics-dashboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/yuusakuri/agent-skills/metrics-dashboard/github.svg)](https://agentmods.dev/skills/yuusakuri/agent-skills/metrics-dashboard)
Your own site
<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/metrics-dashboard"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/metrics-dashboard/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.

agentmods 80×15 button for metrics-dashboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/yuusakuri/agent-skills/metrics-dashboard"><img src="https://agentmods.dev/badge/skills/yuusakuri/agent-skills/metrics-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,247 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01247
Opus 5.5 $0.00019 $0.00499
Sonnet 5.5 $0.00009 $0.00249
Haiku 4.5 $0.00005 $0.00125

Measured 2mo ago against content hash fa74abf49be9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

metrics-dashboard 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.

Origin

This is a copy

100% identical to metrics-dashboard — 0 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.

skills/metrics-dashboard/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Product Metrics Dashboard

Design a comprehensive product metrics dashboard with the right metrics, visualizations, and alert thresholds.

Context

You are designing a metrics dashboard for $ARGUMENTS.

If the user provides files (existing dashboards, analytics data, OKRs, or strategy docs), read them first.

Domain Context

Metrics vs KPIs vs NSM: Metrics = all measurable things. KPIs = a few key quantitative metrics tracked over a longer period. North Star Metric = a single customer-centric KPI that is a leading indicator of business success.

4 criteria for a good metric (Ben Yoskovitz, Lean Analytics): (1) Understandable — creates a common language. (2) Comparative — over time, not a snapshot. (3) Ratio or Rate — more revealing than whole numbers. (4) Behavior-changing — the Golden Rule: "If a metric won't change how you behave, it's a bad metric."

8 metric types: Vanity vs Actionable (only actionable metrics change behavior), Qualitative vs Quantitative (WHAT vs WHY — you need both; never stop talking to customers), Exploratory vs Reporting (explore data to uncover unexpected insights), Lagging vs Leading (leading indicators enable faster learning cycles, e.g. customer complaints predict churn).

5 action steps: (1) Audit metrics against the 4 good-metric criteria. (2) Update dashboards — ensure all key metrics are good ones. (3) Identify vanity metrics — be careful how you use them. (4) Classify leading vs lagging indicators. (5) Pick one problem and dig deep into the data.

For case studies and more detail: Are You Tracking the Right Metrics? by Ben Yoskovitz

Instructions

  1. Identify the metrics framework — organize metrics into layers:

    North Star Metric: The single metric that best captures core value delivery

    Input Metrics (3-5): The levers that drive the North Star

    Health Metrics: Guardrails that ensure overall product health

Read the full file on GitHub · 95 lines

Changes

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.

  1. 2mo ago First seen · 95 lines · 47 tokens per session scan A fa74abf49be9

Subscribe to this mod's changes

metrics-dashboard is a skill published in the GitHub repository yuusakuri/agent-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 47 tokens to every session and 1,247 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to metrics-dashboard, differing in 0 lines, and is treated as a copy.

Analytics and metricsDesign and UX
Related

metrics-dashboard compared with skills from other repositories

metrics-dashboard next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
metrics-dashboardyuusakuri/agent-skillsSkill214d agoMITA47Claude Code
webgl-holographic-foilnexu-io/open-designSkill106kyesterdayApache-2.0A41Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-designSkill106kyesterdayApache-2.0A53Claude Code, Codex
html-ppt-taste-brutalistnexu-io/open-designSkill106kyesterdayApache-2.0A78Claude Code, Codex
visual-ralphYeachan-Heo/oh-my-codexSkill34k3d agoMITA52Codex
glance-canonical-layoutsandroid/skillsSkill10kyesterdayApache-2.0A56Claude Code
accessibilitymicrosoft/hve-coreSkill1.6kyesterdayMITA47Claude Code