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-new-errornpx skills add Bumblebiber/hmem --skill hmem-new-errorgit 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-new-error)<a href="https://agentmods.dev/skills/bumblebiber/hmem/hmem-new-error"><img src="https://agentmods.dev/badge/skills/bumblebiber/hmem/hmem-new-error.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.00069 | $0.00875 |
| Opus 5 | $0.00034 | $0.00438 |
| Sonnet 5 | $0.00014 | $0.00175 |
| Haiku 4.5 | $0.00007 | $0.00088 |
Grade A, and why
hmem-new-error 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/hmem-new-error — New Error Entry
E-entries use a fixed 6-section schema (Analysis → Possible fixes → Fixing attempts → Solution → Cause → Key Learnings). The server auto-scaffolds all sections — you only need to provide a title and a flat description.
The one rule: NO TABS in the description
The parser treats every tab-indented line as a structural node. Tabs in the description accidentally create invalid L2 nodes. Write the description as flat text after a blank line:
✅ write_memory(
prefix="E",
content="Short bug title\n\nFlat description of what went wrong. No tabs here.",
tags=["#project", "#area", "#open"],
links=["P00XX"]
)
❌ write_memory(
prefix="E",
content="Short bug title\n\nDescription:\n\tStep 1 caused X\n\tStep 2 failed",
...
)
The ❌ example creates invalid L2 nodes (Step 1 caused X, Step 2 failed) that fail schema validation.
Step 1: Collect the information
Ask the user (or extract from context):
| Field | Notes |
|---|---|
| Title | Short, descriptive. Max ~50 chars. Format: What broke / where |
| Description | What happened, what was observed. Flat text, no tabs. |
| Tags | At least #open + 2–3 topic tags. |
| Links | Which P-entry does this belong to? (P00XX) |
Step 2: Write the entry
write_memory(
prefix="E",
content="<title>\n\n<flat description>",
tags=["#open", "#tag1", "#tag2"],
links=["P00XX"]
)
The server auto-creates:
- .1 Analysis (your description moves here automatically)
- .2 Possible fixes
- .3 Fixing attempts
- .4 Solution
- .5 Cause
- .6 Key Learnings
The write response shows the created ID (e.g. E0149) and a #open tag.
Step 3: Fill in what you know
Use append_memory to add detail to the sections you can already fill:
append_memory(id="E00XX.1", content="Root cause hypothesis: ...") # Analysis
append_memory(id="E00XX.2", content="Try X first, then Y") # Possible fixes
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 · 103 lines · 69 tokens per session scan A 12a664687850
hmem-new-error is a skill published in the GitHub repository Bumblebiber/hmem (23 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 875 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-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.