dashboard

dashboard is a skill for Claude Code, Codex from bks-lab/open-bridge. It costs 69 tokens per session (842 once invoked), scanned A, original, MIT.

A project-status view shown in the terminal, with optional HTML output. It combines tasks, recent Git activity, and deployment information for the current project or for all configured projects.

In plain words
What is it for?
Use it to see current tasks, recent commits, issue and project information, deployment status, and an overview of multiple projects.
Why use it?
It gathers status from several places so developers do not have to inspect task boards, commits, and deployments separately. It also helps reveal what is active and what has changed recently.

Skill for Claude CodeCodex

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 skills/bks-lab/open-bridge/dashboard
Any agent
npx skills add bks-lab/open-bridge --skill dashboard
Clone the repo
git clone --depth 1 https://github.com/bks-lab/open-bridge

Made for: Claude Code, Codex.

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/skills/bks-lab/open-bridge/dashboard.svg)](https://agentmods.dev/skills/bks-lab/open-bridge/dashboard)
Your own site
<a href="https://agentmods.dev/skills/bks-lab/open-bridge/dashboard"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/dashboard.svg" alt="Measured on agentmods" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 842 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.00069 $0.00842
Opus 5 $0.00034 $0.00421
Sonnet 5 $0.00014 $0.00168
Haiku 4.5 $0.00007 $0.00084

Measured 4d ago against content hash 7d716cbc9265, 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/fetch-project-tasks.sh, scripts/render_dashboard.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/dashboard/SKILL.md · 103 lines

How it starts

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

Dashboard

Render a project dashboard in the terminal showing tasks, recent git activity, and deployment status. Reads project configuration from the Project Registry (workflow/projects/*.yaml) and repo metadata from ecosystem.yaml.

Decision Tree

User wants to...
├── Dashboard for current project    → /dashboard (auto-detect)
├── Dashboard for all projects       → /dashboard --all
├── Dashboard with HTML view         → /dashboard --html
├── Specific project dashboard       → /dashboard {name}
└── Questions about project status   → Answer from data, don't render full dashboard

Commands

Command Behavior
/dashboard Auto-detect project, terminal output
/dashboard --all All projects, global view
/dashboard --html Terminal + HTML in iTerm2 split-pane

Workflow

  1. Detect project — Read references/data-sources.md for the 4-phase auto-detection algorithm (CLAUDE.md section → git remote → CWD → --all)
  2. Fetch data — Read references/data-sources.md § Data Fetching for the 5 parallel data sources (tasks, commits, sparklines, health, issues)
  3. Render terminal — Read references/terminal-rendering.md for layout rules
  4. Render HTML (if --html) — Read references/html-template.md for specs

Terminal Layout (quick reference)

Single-Project

{project.name} Dashboard

╭──────────────────────────────────────────────────────────────────────────╮
│  {Focus: last In-Progress task title or last commit message}             │
│  Last commit {relative_time} on {branch}                                 │
╰──────────────────────────────────────────────────────────────────────────╯

  {repo}    {commit_msg_short}                              {Xh} ago

── Tasks ({n} open) ────────────────────────────────────────────────────────

  #{id}   {title_max40}                      {status}   {assignee}
       + {n} in Backlog

── Git ────────────────────────────────────────────────────────────────────

  {repo_short}   {branch}   {sparkline}   {n} commits (7d)

── Deployment ─────────────────────────────────────────────────────────────

  {app_name}   {status}   build {date}

Read the full file on GitHub · 103 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 103 lines · 69 tokens per session scan A 7d716cbc9265

Subscribe to this mod's changes

dashboard is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed 5d ago), licensed MIT. It adds 69 tokens to every session and 842 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

kungfu-agent-onboarding

Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.

kungfu-systems/kungfu · 49 tokens

planner

Use when the user asks to create, write, or review a docs/plans plan.

tamnguyendinh/Anvien · 20 tokens

repo-bootstrap

Use when the user asks to bootstrap a new repo or project.

tamnguyendinh/Anvien · 16 tokens

swarm-flow

The SDLC router — figures out where a project stands and runs the right phase. Use at the START of any work in a SwarmVault project: continuing/resuming a project, starting a new one, "what's next", or before writing any feature code, spec, design, or ticket. Also use when unsure which phase (requirements, design…

AnmarHani/SwarmVault · 91 tokens

swarm-init

Start a new project connected to the SwarmVault — register it, wire platform adapters, offer git init, set vault-as-default. Use when starting a new project, connecting a project to the vault, or when the user asks to set up SwarmVault in a directory.

AnmarHani/SwarmVault · 60 tokens

swarm-implement

Implementation phase — turn a validated design into dependency-ordered tickets, then work them as one of N parallel agents with atomic claims, model tiering, and tests-in-ticket definition of done. Use to plan tickets from a design, pick up/continue implementation work, coordinate parallel agents, or check what to…

AnmarHani/SwarmVault · 69 tokens