dashboard

dashboard is a command for Claude Code from fatihkan/badi. It costs 0 tokens per session (698 once invoked), scanned A, original, MIT.

A daily statistics panel that reads project notes and Git history, then combines task, audit, incident, failure, and performance data in one table.

In plain words
What is it for?
Use it to review completed, active, waiting, and blocked tasks; inspect audit and incident activity; and count commits and changed lines for the day.
Why use it?
It removes the need to gather daily figures manually from several files and Git commands. It also shows what changed today, including task movement and code changes.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the badi plugin — 81 skills, 86 commands, 30 agents, 7 hooks shipped together

Good fit Use it to review completed, active, waiting, and blocked tasks; inspect audit…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/fatihkan/badi/dashboard
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.

Clone the repo
git clone --depth 1 https://github.com/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

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/fatihkan/badi/dashboard.svg)](https://agentmods.dev/commands/fatihkan/badi/dashboard)
Your own site
<a href="https://agentmods.dev/commands/fatihkan/badi/dashboard"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/dashboard.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 698 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 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.1 $0.00000 $0.00698
Opus 5 $0.00000 $0.00349
Sonnet 5 $0.00000 $0.00140
Haiku 4.5 $0.00000 $0.00070

Measured today against content hash 9f9c3c99326a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 today.

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.

.claude/commands/dashboard.md · 117 lines

How it starts

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

Daily statistics panel. Presents task, audit, event, and performance data as a unified table.

Required Tools

  • Bash (date calculations, file statistics)
  • Read (TaskBoard.md, audit-trail.md, incident-log.md, failure-log.md, daily notes)
  • Grep (data extraction and counting)
  • ...

Data Sources

This command collects data from the following files:

  • TaskBoard.md - Task status information
  • audit-trail.md - Audit trail records
  • incident-log.md - Incident records
  • ...

Section 1: Task Statistics

Step 1: Read the TaskBoard Data

  • Read TaskBoard.md
  • Count the task states:
    • Done (DONE)
    • In Progress (IN_PROGRESS)
    • Waiting (TODO)
    • Blocked (BLOCKED)

Step 2: Today's Task Movement

  • Filter tasks completed today
  • Detect new tasks created today
  • List tasks whose status changed
  • ...

Section 2: Change Statistics

Step 3: Audit Trail Analysis

  • Read audit-trail.md
  • Filter entries matching today's date
  • Extract the changed file count
  • ...

Step 4: Git Statistics

  • Get today's commit count with git log --since="today" --format="%H" | wc -l
  • Compute the change size with git diff --stat HEAD~[count]
  • Report added and removed line counts

Section 3: Incident and Failure Statistics

Step 5: Review the Incident Records

  • Read incident-log.md (if present)
  • Filter today's incidents
  • Extract the severity distribution:
    • CRITICAL: production-impacting
    • HIGH: affects important functionality
    • MEDIUM: limited impact
    • LOW: cosmetic or small issues

Step 6: Review the Failure Records

  • Read failure-log.md (if present)
  • Filter today's failures
  • Detect recurring failure patterns
  • ...

Section 4: Session Length Estimate

Step 7: Duration Calculation

  • Find the first entry in audit-trail.md or the daily notes (session start)
  • Find the last entry (now or the latest activity)
  • Compute the difference
  • ...

Section 5: Weekly Comparison

Step 8: Collect Last Week's Data

  • Find last week's same-day statistics (if available)
  • Comparison metrics:
    • Completed task count
    • Commit count
    • Incident/failure count
    • Work duration

Read the full file on GitHub · 117 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. today First seen · 117 lines · 0 tokens per session scan A 9f9c3c99326a

Subscribe to this mod's changes

dashboard is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 698 tokens. 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-06.