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.
git clone --depth 1 https://github.com/justinjdev/fellowshipWrote 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.
[](https://agentmods.dev/commands/justinjdev/fellowship/dashboard)<a href="https://agentmods.dev/commands/justinjdev/fellowship/dashboard"><img src="https://agentmods.dev/badge/commands/justinjdev/fellowship/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.
<a href="https://agentmods.dev/commands/justinjdev/fellowship/dashboard"><img src="https://agentmods.dev/badge/commands/justinjdev/fellowship/dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.5 | $0.00012 | $0.00172 |
| Sonnet 5.5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
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.
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 statusyourself.
The server keeps running after this command finishes; the user can leave the tab open across the rest of the session.
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.
- 1mo ago First seen · 40 lines · 31 tokens per session scan A d847776f4ca6
dashboard is a command published in the GitHub repository justinjdev/fellowship (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 31 tokens to every session and 431 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-09-06.
Other commands, from other repositories
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.
poc
Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.
ownership
When you need to know who owns a path and who answers for it — the service ownership matrix (team, lead, on-call, SLA) auto-detected from git with CODEOWNERS generated, plus on-call rotations, shift handoffs and escalation paths.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
exception
Signed gate-exception registry — replace ad-hoc --admin / --no-verify bypasses with an auditable, signed, expiring record (who · why · gate · scope · expiry). Create / list / check exceptions.
new-track
Create a new development track with spec, plan, and metadata.