dashboard

dashboard is a command for coding agents from rohitg00/awesome-claude-code-toolkit. It costs 12 tokens per session (343 once invoked), scanned A, original, Apache-2.0.

A command that creates a JSON configuration for a project monitoring dashboard. A monitoring dashboard is a set of charts, numbers, and tables that show software health and activity.

In plain words
What is it for?
Use it to define panels for build results, code activity, test coverage, bugs, technical debt, API speed, errors, uptime, dependencies, and security issues.
Why use it?
It turns a list of useful project measurements into a structured dashboard layout and adds alert thresholds for important problems.

Command

Part of the analytics-reporter plugin — 2 commands shipped together

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/dashboard
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit

Or install analytics-reporter, the plugin that ships this one along with the rest of its 2 commands.

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 dashboard

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/dashboard.svg)](https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/dashboard)
Your own site
<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/dashboard"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/dashboard.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 343 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00012 $0.00343
Opus 5 $0.00006 $0.00171
Sonnet 5 $0.00002 $0.00069
Haiku 4.5 $0.00001 $0.00034

Measured 4d ago against content hash c87ef5d6d919, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugins/analytics-reporter/commands/dashboard.md · 44 lines

What it actually says

Generate a monitoring dashboard configuration for project metrics visualization.

Steps

  1. Determine the dashboard platform (Grafana, Datadog, custom HTML).
  2. Identify key metrics to display:
    • Build health: CI pass rate, build duration trend.
    • Code velocity: Commits per day, PRs merged per week.
    • Quality: Test coverage trend, bug count, tech debt items.
    • Performance: API response times, error rates, uptime.
    • Dependencies: Outdated count, vulnerability count.
  3. Design panel layout:
    • Top row: Key KPIs as single-stat panels.
    • Middle: Time series charts for trends.
    • Bottom: Tables for detailed breakdowns.
  4. Configure data sources and queries for each panel.
  5. Set up alert thresholds on critical metrics.
  6. Export the dashboard configuration as JSON.

Format

{
  "title": "<Project> Dashboard",
  "panels": [
    { "type": "stat", "title": "Build Status", "query": "..." },
    { "type": "graph", "title": "Response Time (P95)", "query": "..." }
  ]
}

Rules

  • Keep dashboards focused with 8-12 panels maximum.
  • Use consistent color coding: green=healthy, yellow=warning, red=critical.
  • Include time range selector defaulting to last 24 hours.
  • Add drill-down links from summary panels to detail views.
  • Document the data source requirements for each panel.
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. 4d ago First seen · 44 lines · 12 tokens per session scan A c87ef5d6d919

Subscribe to this mod's changes

dashboard is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,584 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 343 once invoked, about $0.0001 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.