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 agentmods add commands/skullninja/coco-workflow/dashboardgit clone --depth 1 https://github.com/skullninja/coco-workflowWhat 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 | $0.00022 | $0.01690 |
| Opus 5 | $0.00011 | $0.00845 |
| Sonnet 5 | $0.00004 | $0.00338 |
| Haiku 4.5 | $0.00002 | $0.00169 |
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 2d 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 — 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
- Read
.coco/config.yamlfor:issue_tracker.provider(determines Issue column)pr.enabled(determines PR column)loop.parallel.enabled(determines worktree info in Active line)
- Determine epic:
- If
$ARGUMENTScontains 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
- If
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 tasksdone= count where status iscompletedorclosedin_progress= count where status isin_progressblocked= count where status ispendingAND has unsatisfied dependencies (anydepends_onID that is notcompleted/closed)ready= count where status ispendingAND all dependencies satisfied
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.
- 2d ago First seen · 167 lines · 22 tokens per session scan A bf92edba94ae
dashboard is a command published in the GitHub repository skullninja/coco-workflow (7 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 1,690 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-31.
Other commands, from other repositories
super-dev
Command "super-dev" from shangyankeji/super-dev, covering /super-dev (claude-code), 输入, super dev runtime contract, local knowledge contract and 首轮响应契约(首次触发必须执行).
validate
You are the quality gate. Your job is to verify that a phase's implementation meets quality standards before the team moves to the next phase. No phase should advance until validation passes.
implement
You are the phase dispatcher. Your job is to route implementation work to the correct phase agent with the right context.
progress
You are generating a visual progress report showing which phases are complete, in-progress, or pending for the current feature.
commit
You are creating a conventional commit scoped to the current phase of work.
prd
You are generating a Product Requirements Document (PRD) for the project described below.