Borrowing it
Nothing to install: this file belongs to lancejames221b/agent-hivemind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lancejames221b/agent-hivemind/master/.claude/commands/hv-broadcast.mdgit clone --depth 1 https://github.com/lancejames221b/agent-hivemindWrote 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/lancejames221b/agent-hivemind/hv-broadcast)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-broadcast"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-broadcast.svg" alt="Measured on agentmods" 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.00011 | $0.01384 |
| Opus 5 | $0.00005 | $0.00692 |
| Sonnet 5 | $0.00002 | $0.00277 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
hv-broadcast 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hv-broadcast - Share Critical Findings
Purpose
Broadcast important discoveries, incidents, or findings to all agents in the hAIveMind collective for immediate awareness and coordinated response.
When to Use
- Security Vulnerabilities: Found SQL injection, unauthorized access, or security breaches
- Infrastructure Changes: Load balancer updates, service migrations, configuration changes
- Incident Resolutions: Database deadlocks, service outages, performance issues resolved
- Best Practices: Lessons learned, successful procedures, optimization techniques
- Resource Alerts: High CPU usage, memory leaks, storage capacity warnings
- Deployment Updates: New releases, rollbacks, service updates
Syntax
hv-broadcast "[message]" [category] [severity]
Parameters
- message (required): Clear, actionable description of the finding
- category (required): Type of finding
security: Security vulnerabilities, breaches, patchesinfrastructure: Server changes, network updates, configurationincident: Service outages, performance issues, failuresdeployment: Releases, rollbacks, updatesmonitoring: Alerts, metrics, threshold breachesrunbook: Procedures, scripts, operational updates
- severity (optional): Urgency level (defaults to
info)critical: Immediate action required, system-wide impactwarning: Attention needed, potential impactinfo: General awareness, no immediate action
Real-World Examples
Security Finding
hv-broadcast "SQL injection vulnerability found in auth service /login endpoint - patch deployed" security critical
Result: All security-focused agents immediately begin vulnerability assessment across similar endpoints
Infrastructure Update
hv-broadcast "Load balancer configuration updated with health check intervals changed to 30s" infrastructure info
Result: Monitoring agents adjust alerting thresholds, database agents expect different connection patterns
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.
- 7d ago First seen · 161 lines · 11 tokens per session scan A e606f16fc1d8
hv-broadcast is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,384 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.