A local web dashboard for a fellowship, showing quest progress, approval gates, scouts, groups, event history, notes, and health. It runs on your computer and prints a browser URL.

Use it to monitor progress, review event history, inspect notes, and approve or reject individual or grouped gates.

It puts the current state and pending approvals in one view instead of requiring you to inspect separate command output or files.

dashboard — Command for Claude Code by justinjdev

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/justinjdev/fellowship

Made for: Claude Code.

Or install fellowship, the plugin that ships this one along with the rest of its 20 skills, 20 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/justinjdev/fellowship/dashboard.svg)](https://agentmods.dev/commands/justinjdev/fellowship/dashboard)

Your own site

<a href="https://agentmods.dev/commands/justinjdev/fellowship/dashboard"><img src="https://agentmods.dev/badge/commands/justinjdev/fellowship/dashboard.svg" alt="Measured on agentmods" height="20"></a>

Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 431 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.

Model	Per session	Once invoked
Fable 5.1	$0.00031	$0.00431
Opus 5	$0.00015	$0.00216
Sonnet 5	$0.00006	$0.00086
Haiku 4.5	$0.00003	$0.00043

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

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.

plugin/commands/dashboard.md · 40 lines

What it actually says

Dashboard — Live Fellowship Web UI

Overview

Starts a local HTTP server that shows the current fellowship at a glance: every quest's phase and pending gates, scouts, groups, the event stream, the notes board, and health. Gates can be approved or rejected directly from the page, including batch-approving every pending gate in a group.

Steps

Step 1: Start the Server

Run the binary in the background so it doesn't block the session, redirecting output to a log file:

nohup ~/.claude/fellowship/bin/fellowship dashboard > /tmp/fellowship-dashboard.log 2>&1 &
disown

Defaults to port 3000 and a 5-second poll interval. If the user wants a different port or poll interval, pass flags:

nohup ~/.claude/fellowship/bin/fellowship dashboard --port 3001 --poll 10 > /tmp/fellowship-dashboard.log 2>&1 &
disown

If port 3000 (or the requested port) is already in use — for example a dashboard from a previous session is still running — check /tmp/fellowship-dashboard.log and either reuse the existing dashboard's URL or pick a free port with --port.

Step 2: Report the URL

Print the URL (http://localhost:<port>, 3000 unless overridden) and briefly explain what it shows:

Fellowship dashboard: http://localhost:3000

Live view of every quest's phase and pending gates, scouts, groups (with one-click "Approve All"), the recent event stream, the notes board, and health. Approvals and rejections made on the page take effect immediately — no need to poll fellowship status yourself.

The server keeps running after this command finishes; the user can leave the tab open across the rest of the session.

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.

yesterday First seen · 40 lines · 31 tokens per session scan A d847776f4ca6

Subscribe to this mod's changes

dashboard is a command published in the GitHub repository justinjdev/fellowship (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 431 once invoked, about $0.0002 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-09-06.

Claude Code Multi-Agent Project management ai-agents claude-code-plugin developer-tools prompt-engineering

mega-status

Show detailed status of mega-plan execution including feature progress and story completion. Usage: /plan-cascade:mega-status.

Taoidle/plan-cascade · 23 tokens

hybrid-status

Show execution status of all stories in the PRD. Displays batch progress, individual story states, completion percentage, and recent activity logs.

Taoidle/plan-cascade · 27 tokens

omni-plan

ProductionOS flagship — 13-step orchestrative pipeline with tri-tiered evaluation, recursive convergence, CEO/Eng/Design review chain, CLEAR framework evaluation, multi-model judge tribunal, and autonomous PIVOT/REFINE/PROCEED decisions. Targets 100% production-ready output.

ShaheerKhawaja/ProductionOS · 62 tokens

dashboard