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/PenguinMiaou/claude-hiveWrote 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/penguinmiaou/claude-hive/coordination-status)<a href="https://agentmods.dev/commands/penguinmiaou/claude-hive/coordination-status"><img src="https://agentmods.dev/badge/commands/penguinmiaou/claude-hive/coordination-status/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/penguinmiaou/claude-hive/coordination-status"><img src="https://agentmods.dev/badge/commands/penguinmiaou/claude-hive/coordination-status.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.00017 | $0.00537 |
| Opus 5 | $0.00009 | $0.00269 |
| Sonnet 5 | $0.00003 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
coordination-status 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 8d 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
Context
- COORDINATION.md: !
cat COORDINATION.md 2>/dev/null || echo "NOT FOUND — run /coordination-init first" - CLAUDE.md: !
cat CLAUDE.md 2>/dev/null || echo "NOT FOUND — run /coordination-init first" - Open PRs: !
gh pr list --state open --json number,title,headRefName,isDraft 2>/dev/null || echo "gh CLI not available" - Current branch: !
git branch --show-current - Worktree branches: !
git worktree list 2>/dev/null
Your Task
Display a comprehensive coordination status dashboard. Read all available data and present it clearly.
Output Format
🐝 Claude Hive Status
═══════════════════════
📋 Branch Registry
feat/table-v2 → PR #12 (draft) — scope: lib/table/*
feat/chart-export → PR #13 (ready) — scope: lib/export/*
⚠️ Conflict Map
PR #12 × PR #13 → lib/types/presentation.ts
📦 Merge Queue
1. feat/chart-export #13 — ready to merge
2. feat/table-v2 #12 — still in progress
🧾 Audit Trail
last audit: clean for #12
last audit: blocking review state on #13
📘 Workflow Docs
COORDINATION.md: present
CLAUDE.md: present
🔀 Open PRs (from GitHub)
#12 feat/table-v2 [draft]
#13 feat/chart-export [ready]
💡 Suggested merge order: #13 → #12 (no dependencies)
Rules
- This is READ-ONLY — do not modify any files, branches, or PRs
- If COORDINATION.md doesn't exist, suggest running
/coordination-init - If CLAUDE.md doesn't exist, suggest running
/coordination-init - If there are no branches registered, say "No active branches. Use /worktree-contributor in a work window to get started."
- Cross-reference COORDINATION.md data with actual
gh pr listto detect stale entries - Flag any inconsistencies (e.g., branch in COORDINATION.md but PR closed/missing)
- Include any visible review-decision signals from GitHub when available
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.
- 8d ago First seen · 59 lines · 17 tokens per session scan A c277d223d7b1
coordination-status is a command published in the GitHub repository PenguinMiaou/claude-hive (1 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 537 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
obsidian-projects
Live project status from git + local docs - infers all context from vault notes, no config required.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
portfolio-status
Review the health of all projects in the portfolio.
issues
GitHub-issue marathon - triage open issues, then run agent-ready ones to merge with Agent Teams.
create-task-list-for-issue.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.