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-dispatchnpx skills add Bumblebiber/hmem --skill hmem-dispatchgit 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-dispatch)<a href="https://agentmods.dev/skills/bumblebiber/hmem/hmem-dispatch"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-dispatch.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.00050 | $0.00551 |
| Opus 5 | $0.00025 | $0.00275 |
| Sonnet 5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
hmem-dispatch 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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hmem-dispatch
TRIGGER
Always dispatch for:
- Searching — "does a spec exist?", "find the plan for X", "search the codebase for Y", "check if skill Z covers this", "read the docs for W", "is there already a file that does X?" — any exploration or lookup task
- Calculation or lookup — deterministic, context-free
- Writing an isolated section or document — no conversation history needed
- Writing or modifying code — never write code directly in the main context. Pass the project ID and relevant node IDs (e.g.
.2 Codebase) in the task so the sub-agent can sync them after completing the work. Always include in the task:"Invoke superpowers:coding-discipline before writing code."
Never dispatch for tasks that require knowing the conversation context.
The key rule for searching: if you're about to run grep, find, read, or search_memory to answer a question — dispatch instead. The sub-agent explores, you synthesize the result.
STEP 1: Define the task
Write out before dispatching:
- INPUT: exactly what the sub-agent needs — no more, no less
- TASK: what to do with the input
- OUTPUT FORMAT: what to return
- VERIFY (optional): a concrete shell command that proves completion (e.g.
npx tsc --noEmit,grep "pattern" file.ts). Use for tasks that produce code or file changes.
STEP 2: Dispatch
Send the sub-agent ONLY this prompt — no conversation history, no project context unless the task explicitly requires it:
Task: Input: [If VERIFY set:] After completing the task, run: <VERIFY_CMD> Return your answer in exactly this format: [RESULT] [/RESULT] [If VERIFY set:] [VERIFY_RESULT] pass | fail: [/VERIFY_RESULT] Max 200 words. Use the hmem-subagent skill.
STEP 3: Inject result
Take ONLY the content between [RESULT] and [/RESULT]. If [VERIFY_RESULT] is present: check pass/fail. On fail, report the verification error instead of declaring the task complete. Discard all sub-agent reasoning and preamble. Use the result directly in the main conversation.
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.
- 4d ago First seen · 53 lines · 50 tokens per session scan A 4708ba56f615
hmem-dispatch is a skill published in the GitHub repository Bumblebiber/hmem (24 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 551 once invoked, about $0.0003 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-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.