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 skills add Bumblebiber/hmem --skill hmem-activategit clone --depth 1 https://github.com/Bumblebiber/hmemWrote 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/skills/bumblebiber/hmem/hmem-activate)<a href="https://agentmods.dev/skills/bumblebiber/hmem/hmem-activate"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-activate/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/skills/bumblebiber/hmem/hmem-activate"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-activate.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.00054 | $0.00736 |
| Opus 5.5 | $0.00022 | $0.00294 |
| Sonnet 5.5 | $0.00011 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
hmem-activate 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hmem-activate
TRIGGER
Use when the user switches to a different project mid-session.
STEP 1: Note the currently active project
Before calling load_project, check which project is currently active. The active project is shown in every tool response as Active project: PXXXX <name>.
Note:
- OLD_PROJECT: currently active project ID (e.g. P0043) — or
noneif no project was active - OLD_O: corresponding O-entry (same seq: P0043 → O0043) — if OLD_PROJECT =
none, use O0000 (catch-all for unattributed sessions) - TARGET_PROJECT: the project the user wants to switch to
- TARGET_O: corresponding O-entry (e.g. P0048 → O0048)
STEP 2: Activate the target project
load_project(id: "TARGET_PROJECT")
STEP 3: Check for misrouted exchanges
If OLD_PROJECT ≠ TARGET_PROJECT, exchanges from this session may have been logged to OLD_O instead of TARGET_O.
Check OLD_O for today's exchanges:
read_memory(id: "OLD_O")
Look for session nodes created today (check timestamps). If you find exchanges that belong to the TARGET project's context — i.e. they discuss TARGET project topics, not OLD_PROJECT topics — they are misrouted.
To move them:
move_nodes(node_ids: ["OLD_O.X.Y"], target_o_id: "TARGET_O")
Move at the batch or session level (e.g. O0043.3), not exchange by exchange.
If OLD_O has no today-exchanges, or all exchanges genuinely belong to OLD_PROJECT: skip this step.
STEP 3.5: Noise Check
Scan the load_project output:
- >4k tokens → invoke
hmem-curatefirst - ✓ DONE Roadmap items →
update_memory(id, { irrelevant: true }) - Decommissioned / concept entries in Infrastructure →
update_memory(id, { irrelevant: true })
Fix immediately, do not defer.
STEP 3.6: Schema Check
Scan the load_project output for schema mismatches and fix them immediately.
[-] prefix sections — orphaned nodes outside the current schema (e.g. P0048.10 [-] Bugs (duplicate), P0048.21 [-] Protocol (stale artifact)):
update_memory(id="P00XX.YY", { irrelevant: true })
Mark every [-] section irrelevant. Do not skip, do not defer.
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 · 80 lines · 54 tokens per session scan A f9c6203d496d
hmem-activate is a skill published in the GitHub repository Bumblebiber/hmem (24 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 736 once invoked, about $0.0002 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 skills, from other repositories
ccg-guardian
Use this skill when working on code projects that need memory persistence, code validation, multi-agent coordination, or workflow tracking. Activates Claude Code Guardian MCP tools.
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…
rem-page-org
What an organisation's page in the notebook is made of — the fixed sections, when a company earns a page at all instead of staying a field on a person's, and the rules that keep it from becoming a second copy of everyone who works there. Composed into every stage that writes one.
rem-project-sessions
Write or update one project page from the owner's messages and a bounded packet of local project evidence.
pod-resume
Reconstruct context for a returning developer. Reads .cocoplus/ state and generates a narrative summary of project status, last achievements, pending tasks, recent decisions, available patterns, CocoCupper insights, and recommended next action.