dashboard

dashboard is a command for Claude Code from skullninja/coco-workflow. It costs 22 tokens per session (1,690 once invoked), scanned A, original, MIT.

A progress dashboard is a compact view of an epic, which is a larger body of related work, showing its tasks, dependencies, and execution state. This command also displays pull requests and worktrees when those project settings are enabled.

In plain words
What is it for?
Use it to inspect epic progress, task status, dependency relationships, issue and pull-request state, parallel worktrees, and the current execution session.
Why use it?
It gathers scattered project information into one status view. It makes completed, active, blocked, and next tasks easier to see.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the coco plugin — 6 skills, 14 commands, 4 agents, 3 hooks shipped together

Good fit Use it to inspect epic progress, task status, dependency relationships, issue and pull-request state, parallel worktrees, and the current execution session.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/skullninja/coco-workflow/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/skullninja/coco-workflow

Made for: Claude Code.

Or install coco, the plugin that ships this one along with the rest of its 6 skills, 14 commands, 4 agents, 3 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/skullninja/coco-workflow/dashboard/github.svg)](https://agentmods.dev/commands/skullninja/coco-workflow/dashboard)
Your own site
<a href="https://agentmods.dev/commands/skullninja/coco-workflow/dashboard"><img src="https://agentmods.dev/badge/commands/skullninja/coco-workflow/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 dashboard

Your own site · 80×15
<a href="https://agentmods.dev/commands/skullninja/coco-workflow/dashboard"><img src="https://agentmods.dev/badge/commands/skullninja/coco-workflow/dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,690 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.00022 $0.01690
Opus 5.5 $0.00009 $0.00676
Sonnet 5.5 $0.00004 $0.00338
Haiku 4.5 $0.00002 $0.00169

Measured 1mo ago against content hash bf92edba94ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

commands/dashboard.md · 167 lines

How it starts

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

User Input

$ARGUMENTS

Optional: epic ID. If omitted, auto-detects from open epics.

Setup

  1. Read .coco/config.yaml for:
    • issue_tracker.provider (determines Issue column)
    • pr.enabled (determines PR column)
    • loop.parallel.enabled (determines worktree info in Active line)
  2. Determine epic:
    • If $ARGUMENTS contains an epic ID, use it
    • Otherwise, list all open epics via coco-tracker epic-status
    • If exactly one open epic, use it automatically
    • If multiple, render the Multi-Epic Summary and stop

Execution

1. Gather Data

coco-tracker epic-status {epic-id}
coco-tracker list --json --epic {epic-id}
coco-tracker ready --json --epic {epic-id}

If loop.parallel.enabled is true:

git worktree list --porcelain

If pr.enabled is true:

gh pr list --json number,headRefName,state,reviewDecision,mergedAt --limit 100

Read the most recent session from .coco/tasks/sessions.jsonl (last session_start entry without a matching session_end) to compute session duration.

2. Multi-Epic Summary

If no epic was specified and multiple open epics exist, render this format and stop:

## Active Epics

| Epic     | Feature              | Progress             | Active |
|----------|----------------------|----------------------|--------|
| epic-001 | User Authentication  | ████████░░ 80% 8/10  | 1 task |
| epic-002 | Payment Integration  | ██░░░░░░░░ 20% 2/10  | --     |

Run `/coco:dashboard {epic-id}` for details.

For each epic: count done/total tasks, compute a 10-char progress bar, count in_progress tasks.

3. Compute Progress

From the JSON task list:

  • total = number of tasks
  • done = count where status is completed or closed
  • in_progress = count where status is in_progress
  • blocked = count where status is pending AND has unsatisfied dependencies (any depends_on ID that is not completed/closed)
  • ready = count where status is pending AND all dependencies satisfied

Read the full file on GitHub · 167 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. 1mo ago First seen · 167 lines · 22 tokens per session scan A bf92edba94ae

Subscribe to this mod's changes

dashboard is a command published in the GitHub repository skullninja/coco-workflow (8 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,690 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.

Related

Other commands, from other repositories

ccc

CC Commander Hub — interactive menu derived from adventure JSON files. 450+ skills, 11 CCC domains, 80+ commands, 9 modes.

KevinZai/commander · 31 tokens

ccc-spawn

Plan and launch parallel Claude Code peers (quick, team, swarm or domain expert), each on its own branch and worktree with non-overlapping files, then track or stop them. Use when work splits into independent parts that should run in separate sessions.

KevinZai/commander · 55 tokens

ccc-improve

Run the continuous-improvement pipeline: scan GitHub and npm for new Claude Code tooling, score proposals, and approve or reject them in a local queue. Use when reviewing ecosystem findings or deciding what to adopt next.

KevinZai/commander · 47 tokens

ccc-linear

Show the Linear project board by status with a progress bar, pick an issue to start work on, or create a new issue, with every Linear write confirmed first. Use when you want to see or act on your Linear project from the session or the ccc CLI.

KevinZai/commander · 54 tokens

ccc-makeover

Score project health with X-Ray, apply the top recommendations in impact order with your OK for each, and show the before and after score. Use when you want the highest-impact project health fixes applied and measured.

KevinZai/commander · 47 tokens

ccc-office-hours

Stress-test a product idea before writing code through product, technical and user lenses, ending in BUILD IT, SIMPLIFY FIRST, RESEARCH MORE or KILL IT. Use when deciding whether a feature or product is worth building.

KevinZai/commander · 50 tokens