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-installgit 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-install)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-install"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-install.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 | $0.00011 | $0.02254 |
| Opus 5 | $0.00005 | $0.01127 |
| Sonnet 5 | $0.00002 | $0.00451 |
| Haiku 4.5 | $0.00001 | $0.00225 |
Grade B, and why
hv-install 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 5d 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.
→ Fix ownership: sudo chown $USER:$USER ~/.claude/commands Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
→ Check MCP server: curl http://localhost:8900/health How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hv-install - hAIveMind Setup and Updates
Purpose
Install, update, or manage hAIveMind command suite and agent configuration for seamless integration with the collective intelligence system.
When to Use
- First Time Setup: Initialize hAIveMind on new development environment
- Command Updates: Install latest command versions from collective
- Project Integration: Set up hAIveMind for specific projects
- Troubleshooting: Clean install to resolve command issues
- Agent Registration: Register new agent with specialized capabilities
- Configuration Sync: Update CLAUDE.md with hAIveMind integration
Syntax
hv-install [target] [options]
Parameters
- target (optional): Installation scope
personal: Install to personal commands (~/.claude/commands/)project: Install to project commands (.claude/commands/)clean: Remove and reinstall all commands freshstatus: Show current installation status only- (no target): Smart detection based on current directory
- options (optional):
--force: Force reinstall even if up-to-date--quiet: Minimal output, errors only--dry-run: Show what would be installed without making changes
Installation Process
Smart Detection (No Arguments)
- Context Analysis: Check if in project directory or personal environment
- Existing Installation: Detect current commands and versions
- Capability Assessment: Determine agent role based on system type
- Optimal Configuration: Choose best installation strategy
Location-Specific Installation
- Personal (~/.claude/commands/): Global commands available across all projects
- Project (.claude/commands/): Project-specific commands with custom configuration
- Hybrid: Personal base + project-specific overrides
Real-World Examples
First Time Setup on Development Machine
hv-install personal
Result: Installs all hv-* commands to personal directory, registers as development agent, sets up collective connectivity
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.
- 5d ago First seen · 276 lines · 0 tokens per session scan B fddae7bab4f2
hv-install 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 2,254 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.
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.