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-sync-hooksgit 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-hooks)<a href="https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-sync-hooks"><img src="https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-sync-hooks.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.00000 | $0.00619 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
hv-sync-hooks 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 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.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hv-sync-hooks
Automated ticket-memory synchronization with pre/post work hooks integration.
Usage
/hv-sync-hooks status
/hv-sync-hooks trigger <event_type> [ticket_id] [project_id]
/hv-sync-hooks sync-with-hooks [command_type] [--force] [--verbose]
Commands
Status Check
/hv-sync-hooks status
Get current status of registered sync hooks, protocol version, and execution history.
Manual Hook Trigger
/hv-sync-hooks trigger pre_work WEBTESTS-1 memory-mcp-project
/hv-sync-hooks trigger post_work WEBTESTS-1 memory-mcp-project --results "Completed web testing setup"
Manually trigger sync hooks for testing or recovery purposes.
Sync with Hooks
/hv-sync-hooks sync-with-hooks install_sync --verbose
/hv-sync-hooks sync-with-hooks install_commands --force
Execute sync commands with automated pre/post hooks integration.
Features
- Automated Pre-Work Hooks: Capture ticket context, check related memories, store work intentions
- Automated Post-Work Hooks: Store completion results, document lessons learned, broadcast discoveries
- Network Sync Integration: Hooks automatically integrate with existing install_sync and install_commands
- Zero Manual Overhead: Hooks trigger automatically on ticket status changes (when configured)
- hAIveMind Knowledge Sharing: Results automatically shared across the collective intelligence network
Integration with Existing Commands
The sync hooks system integrates seamlessly with existing hAIveMind commands:
- hv-sync: Now includes automatic pre/post hooks when used with --hooks flag
- hv-install: Command installation now triggers knowledge synchronization hooks
- hv-broadcast: Hook results can be automatically broadcast to the collective
- hv-delegate: Task delegation can trigger coordination hooks
Configuration
Sync protocol is configured via sync-protocol.json:
{
"protocol_version": "1.0",
"compliance_level": "REQUIRED",
"auto_remind": true,
"pre_sync_checklist": [
"Read ticket description and current status",
"Check hAIveMind memory for related context",
"Store work intention with expected outcomes"
],
"post_sync_checklist": [
"Update ticket status with detailed completion notes",
"Store comprehensive results in hAIveMind memory",
"Document lessons learned and troubleshooting solutions"
]
}
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 · 84 lines · 0 tokens per session scan A f16d5af67d3f
hv-sync-hooks is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 619 tokens. 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
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.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
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.