What is hv-sync-hooks?

A command that keeps work tickets and shared task notes in sync around the start and end of coding work. It can check, trigger, and connect these updates to existing setup commands.

Use it to inspect synchronization hooks, test or recover them, and run installation commands with automatic pre-work and post-work updates.

It reduces the need to record task context, intentions, results, and lessons by hand. This helps keep ticket history and shared memory current.

How lancejames221b/agent-hivemind configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/lancejames221b/agent-hivemind/master/.claude/commands/hv-sync-hooks.md

Clone the repo

git clone --depth 1 https://github.com/lancejames221b/agent-hivemind

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lancejames221b/agent-hivemind/hv-sync-hooks/github.svg)](https://agentmods.dev/commands/lancejames221b/agent-hivemind/hv-sync-hooks)

Your own site

<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 619 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.00619
Opus 5.5	$0.00000	$0.00248
Sonnet 5.5	$0.00000	$0.00124
Haiku 4.5	$0.00000	$0.00062

Measured 2mo ago against content hash f16d5af67d3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/commands/hv-sync-hooks.md · 84 lines

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"
  ]
}

Read the full file on GitHub · 84 lines

Changes

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.

2mo ago First seen · 84 lines · 0 tokens per session scan A f16d5af67d3f

Subscribe to this mod's changes

hv-sync-hooks is a command published in the GitHub repository lancejames221b/agent-hivemind (7 stars, last pushed 3mo 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.

Memory and context Project management

hv-sync-hooks next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
hv-sync-hookslancejames221b/agent-hivemind	Command	7	3mo ago	MIT	A	0	Claude Code
minutes-ideassilverstein/minutes	Command	1.6k	yesterday	MIT	A	48	Claude Code, OpenCode
learnReflexioAI/claude-smart	Command	791	3d ago	Apache-2.0	A	14	Claude Code
memory-storeverygoodplugins/mcp-automem	Command	66	yesterday	MIT	A	10	Claude Code
analyze-contextRohiRIK/OpenLtm	Command	29	8d ago	MIT	A	39	Claude Code
cc-memoryTheLobbi/claude	Command	21	7d ago	MIT	A	0	Claude Code
lians-recallLians-ai/Lians	Command	17	5d ago	Apache-2.0	A	19	Claude Code

agent-hivemind: Command for Claude Code