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 commands/lancejames221b/agent-hivemind/hv-statusgit 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-status)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-status"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-status.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.00014 | $0.03534 |
| Opus 5 | $0.00007 | $0.01767 |
| Sonnet 5 | $0.00003 | $0.00707 |
| Haiku 4.5 | $0.00001 | $0.00353 |
Grade B, and why
hv-status scanned grade B with 2 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 6d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
4. Restart services: ssh elastic2 'sudo systemctl restart memory-mcp-server' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. Verify MCP server: curl http://elastic2:8900/health How it starts
The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hv-status - Collective Health Monitor
Purpose
Comprehensive monitoring of hAIveMind collective health including agent availability, memory utilization, network connectivity, and system performance metrics.
When to Use
- Daily Health Checks: Monitor collective operational status
- Troubleshooting Issues: Diagnose connectivity or performance problems
- Capacity Planning: Monitor memory usage and agent workload
- Network Monitoring: Check Tailscale connectivity between agents
- Before Delegating: Verify target agents are available and responsive
- Performance Analysis: Understand collective resource utilization
Syntax
hv-status [options]
Parameters
- options (optional): Display filtering and formatting
--detailed: Show comprehensive information for all sections--agents: Show only agent roster and availability--memory: Show only memory statistics and usage--network: Show only network connectivity status--json: Output in JSON format for programmatic use--quiet: Show only critical issues, minimal output
Status Information Sections
Agent Roster and Availability
- Active Agents: Currently online and responding
- Agent Capabilities: Skills and expertise each agent provides
- Response Times: Average response latency for each agent
- Workload Status: Current task queue and availability
- Last Seen: When each agent was last active
Memory Statistics
- Storage Utilization: ChromaDB and Redis usage metrics
- Memory Categories: Distribution across infrastructure, incidents, etc.
- Growth Trends: Memory usage over time
- Cache Performance: Redis hit rates and efficiency
- Cleanup Status: Old memory removal and optimization
Network Health
- Tailscale Connectivity: Connection status to each machine
- API Endpoints: Health check status for MCP servers
- Sync Performance: Inter-machine synchronization latency
- Certificate Status: SSL/TLS certificate validity
- Firewall Status: Port accessibility between nodes
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.
- 6d ago First seen · 321 lines · 0 tokens per session scan B 7178f28d5904
hv-status is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 3,534 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.