Hivemind is a shared memory system for coding agents that records their sessions and turns recurring solutions into reusable skills. Teams use it to let agents search past traces, share learned procedures across tools and machines, and keep the resulting knowledge in their own cloud or on-premises storage. The catalogue entries are Hivemind's own skills, hooks, plugins, and commands for connecting agents to that shared memory.
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.
git clone --depth 1 https://github.com/activeloopai/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/activeloopai/hivemind/update)<a href="https://agentmods.dev/commands/activeloopai/hivemind/update"><img src="https://agentmods.dev/badge/commands/activeloopai/hivemind/update/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.
<a href="https://agentmods.dev/commands/activeloopai/hivemind/update"><img src="https://agentmods.dev/badge/commands/activeloopai/hivemind/update.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00132 |
| Opus 5.5 | $0.00004 | $0.00053 |
| Sonnet 5.5 | $0.00002 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
update 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 1mo 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.
What it actually says
First refresh the marketplace cache, then update:
claude plugin marketplace update hivemind 2>/dev/null; claude plugin update hivemind --scope user 2>/dev/null; claude plugin update hivemind --scope project 2>/dev/null; claude plugin update hivemind --scope local 2>/dev/null; claude plugin update hivemind --scope managed 2>/dev/null; echo "Done."
Tell the user to run /reload-plugins to apply the update.
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.
- 1mo ago First seen · 13 lines · 11 tokens per session scan A 290f14a9a5ea
update is a command published in the GitHub repository activeloopai/hivemind (1,628 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 132 once invoked, about $0.0000 per session on Opus 5.5. 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-30.
Other commands, from other repositories
cairn-resume
Resume an active Cairn task after /clear. Reads the task journal + spec and primes context cold.
cairn-init
Adopt this project with Cairn — runs the one-time init pipeline inline.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).
plan
Show or update the work ledger — what is done, in flight, and next.
reflect
Synthesize patterns and a progress summary from milepost entries.
briefing
Morning summary. Show the user where things stand so they can pick up where they left off. This is the "catch me up" command.