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 agentmods add skills/bumblebiber/hmem/hmem-session-startnpx skills add Bumblebiber/hmem --skill hmem-session-startgit 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-session-start)<a href="https://agentmods.dev/skills/bumblebiber/hmem/hmem-session-start"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-session-start.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.01837 |
| Opus 5 | $0.00042 | $0.00919 |
| Sonnet 5 | $0.00017 | $0.00367 |
| Haiku 4.5 | $0.00008 | $0.00184 |
Grade A, and why
hmem-session-start 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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hmem-session-start
TRIGGER
Run at the beginning of any session, after /clear, and after any load_project call.
CONTEXT: Pre-injected by hook
All stable context is PRE-INJECTED by the hmem-startup.sh hook:
- H-entries (H0008 Identität, H0005 Arbeitsstil, H0003 IT-Skills, H0007 Präferenzen, etc.)
- Recent projects (--- Recent projects --- block)
- Device info (--- Active device --- block)
- Sync status (--- hmem-sync --- block)
- Infrastructure favorites (--- Infrastructure --- block)
- Checkpoint status
Do NOT call read_memory(mode='essentials') — it's redundant and slow.
STEP 1: Activate project
If the user's message names a specific project (e.g. "lade Projekt hmem", "P0048"): call load_project(id: "P00XX").
If the user did NOT name a project: list the 5 entries from the --- Recent projects --- block as bullet points, ask which one. Once picked, call load_project(id: "P00XX").
load_project returns the project brief, recent O-Entry summaries, rules, lessons. load_project is the only activation action — no separate read_memory.
STEP 2: Pending-work check (git repo state)
Sessions resume after days or weeks — pending work rots if nobody surfaces it.
Find the repo
Look in load_project output for a filesystem path (.1.4 Environment / .2 Codebase). If no .git, skip.
Run the checks (parallel)
git status --porcelain
git stash list
git worktree list
git for-each-ref --format='%(refname:short) %(committerdate:relative)' refs/heads/ | grep -v '^main\b\|^master\b'
git branch --no-merged main 2>/dev/null || git branch --no-merged master
Cross-reference: branch in for-each-ref AND --no-merged = real unmerged commits.
Surface
Only when something is pending. German format:
⚠ Offene Arbeit im Repo:
Worktrees:
.worktrees/<name> — Branch <branch>, letzter Commit <relative date>
Stashes:
stash@{0}: <message> (<relative date>)
Unmerged Branches:
<branch> — <N> Commits voraus, letzter Commit <relative date>
Uncommitted auf <current branch>:
<file>, <file>, ...
Weiter dran arbeiten oder aufräumen?
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.
- 5d ago First seen · 187 lines · 83 tokens per session scan A f27f6f238746
hmem-session-start is a skill published in the GitHub repository Bumblebiber/hmem (23 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 1,837 once invoked, about $0.0004 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.
Other skills, from other repositories
kayba-ace
This skill ships learnfromtraces.py, a script that reads OpenClaw session transcripts, feeds them through the ACE learning pipeline, and writes an updated skillbook to disk.
rekal-init
Bootstrap rekal memory for a project. Scans the codebase for architecture, conventions, dependencies, workflows, and config, then stores durable knowledge as properly typed, tagged, deduplicated memories. Use when starting rekal on a new project, or when user says "init rekal", "bootstrap memory", "populate rekal"…
rekal-save
End-of-session memory capture with deduplication. Extracts durable knowledge, checks for duplicates, stores or replaces as appropriate. Use whenever a session wraps up, a task finishes, or the user says goodbye/thanks/done. Also use when significant preferences, decisions, or discoveries emerge mid-session. Make sure…
rekal-usage
Operational guide for rekal memory tools. Precise rules for when/how to call each tool, with exact parameters and decision trees. Use at session start, when onboarding to a rekal workspace, or when user asks "how do I use rekal", "what rekal tools", "help with memory". Trigger: /rekal-usage.
rekal-hygiene
Periodic memory maintenance and cleanup. Finds duplicates, contradictions, and quality issues in the memory database. Proposes fixes for user approval. Never auto-deletes or auto-modifies. Use when user says "clean up memories", "memory maintenance", "check memory health", or invokes /rekal-hygiene. Run monthly or…
vault-for-llm
Connect OpenClaw to Vault Agent Memory as a local-first governed project memory layer. Search first, then bounded-read cited source ranges; propose new memories as candidates instead of writing directly into active memory.