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-releasegit 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-release)<a href="https://agentmods.dev/skills/bumblebiber/hmem/hmem-release"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-release/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-release"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-release.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.00050 | $0.03061 |
| Opus 5.5 | $0.00020 | $0.01224 |
| Sonnet 5.5 | $0.00010 | $0.00612 |
| Haiku 4.5 | $0.00005 | $0.00306 |
Grade A, and why
hmem-release 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/hmem-release — Release Checklist
Run this checklist before every npm publish of hmem. Every release touches code, skills, config, and documentation — this skill ensures nothing falls through the cracks.
Step 0: Get Explicit Permission (R0027)
Always pause before proceeding. Even when the user invoked this skill, get explicit go-ahead for this specific release. Don't infer approval from prior context — "apply the changes" is not "publish".
Show the user:
- Current version → target version
- Bump type (patch / minor / major) and the reason
- Short summary of what's changing (1-3 bullets)
Then ask: "Soll ich publishen?" / "OK to release?" — wait for an explicit yes. If the user pauses, defers, or says "noch nicht", stop and do not run any further steps. The fact that the user asked you to prepare a release is not permission to ship it.
Step 1: Version Bump
npm version patch --no-git-tag-version # or minor/major as appropriate
Decide the version type based on what changed:
- patch: bugfixes, skill text updates, small improvements
- minor: new features (new tools, new prefix, new config options, new skills)
- major: breaking changes (schema changes, removed tools, API changes)
Step 2: Build & Type Check
npx tsc --noEmit # type check first (fast)
npx tsc # full build
Fix any errors before proceeding.
Step 3: Skill Audit
Every code change can affect skill documentation. Check each skill against the current code:
| Skill | Check for | Common triggers |
|---|---|---|
| hmem-write | write_memory format, body syntax (>), char limits, tag rules |
Changes to parseTree, write(), validation logic |
| hmem-read | read_memory output format, load_project display, O-entry format | Changes to formatBulkRead, formatRecentOEntries, load_project rendering |
| hmem-config | New config parameters, changed defaults, removed options | Changes to HmemConfig interface, DEFAULT_CONFIG, loadHmemConfig |
| hmem-update | All user-facing changes: new MCP tools, removed tools, new CLI commands, statusline changes, new config options, behavior changes, setup steps. This is the changelog users read when upgrading. | Every release — if a user upgrading needs to know about it, it goes here. |
| hmem-curate | Curation rules (self + foreign-file), hmem_path param, new node types, new tags | New tagged node types (#checkpoint-summary, #skill-dialog), schema changes, hmem_path-capable tool changes |
| hmem-new-project | P-entry schema (R0009), write_memory format | Changes to P-entry structure or write format |
| hmem-setup | Hook scripts, init flow, MCP config format | Changes to hooks, CLI commands, environment variables |
| hmem-wipe | Checkpoint references, context threshold | Changes to checkpointMode, contextTokenThreshold |
| hmem-sync-setup | Sync config format, sync commands | Changes to sync parsing, hmem-sync integration |
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 · 245 lines · 50 tokens per session scan A f6d5d56055f1
hmem-release is a skill published in the GitHub repository Bumblebiber/hmem (24 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 3,061 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
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
release
Cut a release of steam-games-mcp — draft CHANGELOG entries, check docs/metadata consistency, then bump/tag/push. Use when asked to release, cut a version, or publish a new version of this package.
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…