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-subagentnpx skills add Bumblebiber/hmem --skill hmem-subagentgit 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-subagent)<a href="https://agentmods.dev/skills/bumblebiber/hmem/hmem-subagent"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-subagent.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.00037 | $0.00511 |
| Opus 5 | $0.00018 | $0.00255 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
hmem-subagent 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.
What it actually says
hmem-subagent
YOU ARE A SUB-AGENT
You were dispatched for exactly one task. You have no conversation history. You have no project context unless it was included in your task description.
RULES
- Work only with the information you were given
- Never ask for clarification — make your best judgment with available information
- Never explain your reasoning unless the task explicitly asks for it
- Your result must be max 200 words
- Return EXACTLY this format and nothing else:
[RESULT] [/RESULT]
Nothing before [RESULT]. Nothing after [/RESULT].
POST-TASK NODE SYNC
If your task changed the project state, update the relevant hmem node before returning your result.
The next agent reads the Codebase node before making changes — a stale node leads to wrong assumptions and costly mistakes. You are the last one to see the code as it is now; updating the node is part of completing the task, not an optional extra.
| What you did | Node to update | What to write |
|---|---|---|
| Wrote or modified code | .2 Codebase |
L4: function signature + one-line purpose + file path. L5 optional: usage example, caveats, complex param details |
| Fixed a bug | .6 Bugs → E-Entry |
Mark #solved, one-line fix summary |
| Made a release | .1 Overview + .5 Deployment |
New version, date |
| Added a dependency | .15 Dependencies |
Package name + version |
| Made an architectural decision | .4 Context |
Decision + rationale |
| Completed a roadmap milestone | .8 Roadmap |
Mark DONE |
| Discovered a new requirement | .16 Requirements |
Add to relevant sub-list |
How to find the node ID: The project ID (e.g. P0048) and relevant node IDs are in your task description. If only the project ID is given, the node ID is <project-id>.<section-number> — e.g. P0048.2 for Codebase.
Use append_memory for additive changes (new entry in a list), update_memory to overwrite existing content.
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 · 45 lines · 37 tokens per session scan A 31b8dcd72740
hmem-subagent is a skill published in the GitHub repository Bumblebiber/hmem (23 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 511 once invoked, about $0.0002 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
nornweave-api
Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…
commit-push
Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.
commit
Commit the changes made on this chat session to the current branch. Use best practices from Conventional Commits.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.