hivemind-memory

A shared, persistent store of notes about previous sessions, projects, and team knowledge.

In plain words
What is it for?
Use it to look up earlier discussions, project history, organization knowledge, and information saved by other sessions or agents.
Why use it?
It prevents useful context from being lost between sessions and helps the agent recall decisions or past work. It also requires checking both the built-in memory and this shared memory.

Skill for Claude CodeCodex

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 skills/activeloopai/hivemind/deeplake-memory
Any agent
npx skills add activeloopai/hivemind --skill deeplake-memory
Clone the repo
git clone --depth 1 https://github.com/activeloopai/hivemind

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,471 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00033 $0.01471
Opus 5 $0.00016 $0.00736
Sonnet 5 $0.00007 $0.00294
Haiku 4.5 $0.00003 $0.00147

Measured 2d ago against content hash 5ed1bc70836c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hivemind-memory 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 2d 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.

Only use bash commands (cat, ls, grep, echo, jq, head, tail, sed, awk, etc.) to interact with `~/.deeplake/memory/`. Do NOT use python, python3, node, curl, or other interpreters — they are not available in the memory fi
harnesses/codex/skills/deeplake-memory/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Hivemind Memory

You have persistent memory at ~/.deeplake/memory/ — global memory shared across all sessions, users, and agents in the org.

Memory Structure

~/.deeplake/memory/
├── index.md                          ← START HERE — table of all sessions
├── summaries/
│   ├── session-abc.md                ← AI-generated wiki summary
│   └── session-xyz.md
└── sessions/
    └── username/
        ├── user_org_ws_slug1.jsonl   ← raw session data
        └── user_org_ws_slug2.jsonl
  1. First: Read ~/.deeplake/memory/index.md — quick scan of all sessions with dates, projects, descriptions
  2. If you need details: Read the specific summary at ~/.deeplake/memory/summaries/<session>.md
  3. If you need raw data: Read the session JSONL at ~/.deeplake/memory/sessions/<user>/<file>.jsonl
  4. Keyword search: grep -r "keyword" ~/.deeplake/memory/

Do NOT jump straight to reading raw JSONL files. Always start with index.md and summaries.

Organization Management

Each argument is separate — do NOT quote subcommands together. The auth command is at $PLUGIN_ROOT/bundle/commands/auth-login.js (or check the session context for the resolved path):

  • node "<path>/auth-login.js" login — SSO login
  • node "<path>/auth-login.js" whoami — show current user/org
  • node "<path>/auth-login.js" org list — list organizations
  • node "<path>/auth-login.js" org switch <name-or-id> — switch organization
  • node "<path>/auth-login.js" workspaces — list workspaces
  • node "<path>/auth-login.js" workspace <id> — switch workspace
  • node "<path>/auth-login.js" invite <email> <ADMIN|WRITE|READ> — invite member (ALWAYS ask user which role first)
  • node "<path>/auth-login.js" members — list members
  • node "<path>/auth-login.js" remove <user-id> — remove member
  • node "<path>/auth-login.js" --help — show all commands

Skill Management (skillify)

Hivemind can mine reusable skills from agent session logs and share them across your team. Each argument is separate — do NOT quote subcommands together.

Read the full file on GitHub · 102 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.

  1. 2d ago First seen · 102 lines · 33 tokens per session scan A 5ed1bc70836c

Subscribe to this mod's changes

hivemind-memory is a skill published in the GitHub repository activeloopai/hivemind (1,593 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 1,471 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

design-is

Audit a design against Dieter Rams' ten "Good design is..." principles, then hand off a /make-plan prompt for one of three outcomes — new design, refine design, or redesign. Use when the user says "audit this design", "design review", "check this UI against Rams", "is this UI good", "critique this design", "design…

thedotmack/claude-mem · 91 tokens

weekly-digests

Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…

thedotmack/claude-mem · 93 tokens

oh-my-issues

Cluster a GitHub issue backlog by root cause into a small set of plan-master issues, redirect children with a standardized comment, and bundle architectural-fix PRs that close clusters atomically. Use when an issue tracker has accumulated dozens of reports that share underlying defects, when asked to triage /…

thedotmack/claude-mem · 97 tokens

timeline-report

Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.

thedotmack/claude-mem · 47 tokens

mode-creator

Interactively create, install, activate, and verify custom claude-mem modes, including domain-specific observation types, concept tags, optional Telegram alerts, bot setup, worker restart, and startup-context verification. Use this whenever someone asks to customize what claude-mem remembers, create or change a mode…

thedotmack/claude-mem · 94 tokens

smart-explore

Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.

thedotmack/claude-mem · 41 tokens