update

A command that updates the Hivemind plugin across its available installation scopes.

In plain words
What is it for?
Use it when you need to refresh the plugin marketplace data, install the latest Hivemind version, and then reload plugins.
Why use it?
It keeps the plugin current without requiring separate update commands for each possible scope.

Command

Install

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.

agentmods
npx agentmods add commands/activeloopai/hivemind/update
Clone the repo
git clone --depth 1 https://github.com/activeloopai/hivemind
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 132 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00132
Opus 5 $0.00005 $0.00066
Sonnet 5 $0.00002 $0.00026
Haiku 4.5 $0.00001 $0.00013

Measured yesterday against content hash 290f14a9a5ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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.

harnesses/claude-code/commands/update.md · 13 lines

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.

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.

  1. yesterday First seen · 13 lines · 11 tokens per session scan A 290f14a9a5ea

Subscribe to this mod's changes

update is a command published in the GitHub repository activeloopai/hivemind (1,590 stars, last pushed 11d ago), licensed Apache-2.0. It adds 11 tokens to every session and 132 once invoked, about $0.0001 per session on Opus 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.