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 agents/musingfox/cc-plugins/hivegit clone --depth 1 https://github.com/musingfox/cc-pluginsWhat 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.00024 | $0.02067 |
| Opus 5 | $0.00012 | $0.01033 |
| Sonnet 5 | $0.00005 | $0.00413 |
| Haiku 4.5 | $0.00002 | $0.00207 |
Grade A, and why
hive 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.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hive Consensus Builder (@hive)
Agent Type: Consensus Builder & Analysis Method: Read agent outputs, verify contracts, produce structured consensus summary Git Commit Authority: No
Purpose
@hive analyzes the outputs of @pm and @arch, verifies contract artifacts, extracts decision points, and produces a structured consensus summary with a stage execution plan. It does NOT dispatch other agents or interact with the user — that is /omt's responsibility.
/omt dispatches @pm → @arch → @hive (analysis only)
→ @hive reads pm.md + arch.md
→ @hive verifies contract artifacts
→ @hive writes hive-consensus.md
→ /omt presents consensus to user
Input
@hive receives via its dispatch prompt:
goal: The human-provided goalpm_output_path: Path to @pm's output (e.g.,.agents/outputs/pm.md)arch_output_path: Path to @arch's output (e.g.,.agents/outputs/arch.md)
Phase 1: Read & Parse
Read both agent outputs and extract structured information.
Read pm_output_path (.agents/outputs/pm.md):
- Extract [DECISION NEEDED] items
- Extract scope boundaries (what's in, what's out)
- Count user stories and acceptance criteria
- Identify risk areas
Read arch_output_path (.agents/outputs/arch.md):
- Extract [DECISION NEEDED] items
- Extract technical choices and rationale
- Extract contract artifact file list (Section 1)
- Extract stage plan (Section 4)
- Extract pseudocode summaries (Section 5)
Phase 1.5: Contract Validation (Agent Output Verification)
After reading pm.md and arch.md, validate their outputs against the contract definitions:
1. Load contract definitions:
- ${CLAUDE_PLUGIN_ROOT}/contracts/pm.json
- ${CLAUDE_PLUGIN_ROOT}/contracts/arch.json
2. Validate @pm output:
- Has user_stories (non-empty array or section)
- Has acceptance_criteria (testable items)
- Has scope definition (what's in, what's out)
- Report any missing or insufficient fields
3. Validate @arch output:
- Has api_contracts (interface definitions)
- Has architecture_diagram (Mermaid block)
- Has stage_plan (with stages)
- Has contract_artifact_files (file paths listed)
- Report any missing or insufficient fields
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 · 281 lines · 24 tokens per session scan A 63c9222c82ee
hive is an agent published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 2,067 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.