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-syncgit 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-sync)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-sync"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-sync.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.00015 | $0.02017 |
| Opus 5 | $0.00008 | $0.01009 |
| Sonnet 5 | $0.00003 | $0.00403 |
| Haiku 4.5 | $0.00002 | $0.00202 |
Grade A, and why
hv-sync scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. Check MCP server: curl http://lance-dev:8900/health How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hv-sync - Collective Synchronization
Purpose
Synchronize local hAIveMind installation with the collective, ensuring commands, configurations, and agent state are up-to-date across all nodes.
When to Use
- Regular Updates: Keep commands and configs current with collective
- After Network Issues: Resync after connectivity problems
- New Agent Setup: Initial sync for new agent registration
- Troubleshooting: Clean sync to resolve configuration issues
- Manual Updates: Force sync when automatic updates fail
- Status Checking: Verify current sync state and version info
Syntax
hv-sync [operation] [options]
Parameters
- operation (optional): Sync operation type
force: Force full resync regardless of current statestatus: Show sync status without making changesclean: Remove local state and perform fresh sync- (no operation): Smart sync based on current state
- options (optional):
--verbose: Show detailed progress during sync--commands: Sync only command files--config: Sync only configuration files--memory: Sync only memory/agent state--hooks: Enable automatic pre/post sync hooks for ticket-memory synchronization--dry-run: Show what would be synced without making changes
Real-World Examples
Regular Update Check
hv-sync
Result: Smart sync that only updates changed components
Force Complete Resync
hv-sync force --verbose
Result: Downloads all commands and configs regardless of current versions
Check Sync Status Only
hv-sync status
Result: Shows version comparisons and sync timestamps without making changes
Clean Slate Resync
hv-sync clean
Result: Removes local state and performs complete fresh installation
Commands-Only Update
hv-sync --commands --verbose
Result: Updates only hv-* command files with detailed progress
Sync with Automated Hooks
hv-sync --hooks --verbose
Result: Performs sync with automatic pre/post hooks for ticket-memory synchronization
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.
- 4d ago First seen · 227 lines · 0 tokens per session scan A 3d74902adf18
hv-sync is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 2,017 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.