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 Republicofhaitigoodstory6175/engram --skill mistakesgit clone --depth 1 https://github.com/Republicofhaitigoodstory6175/engramWrote 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/republicofhaitigoodstory6175/engram/mistakes)<a href="https://agentmods.dev/skills/republicofhaitigoodstory6175/engram/mistakes"><img src="https://agentmods.dev/badge/skills/republicofhaitigoodstory6175/engram/mistakes/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/republicofhaitigoodstory6175/engram/mistakes"><img src="https://agentmods.dev/badge/skills/republicofhaitigoodstory6175/engram/mistakes.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.00046 | $0.00726 |
| Opus 5 | $0.00023 | $0.00363 |
| Sonnet 5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
mistakes 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 12d 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.
This is a copy
100% identical to mistakes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
engram mistakes
Surface bi-temporal mistake memory from engram's graph. Each mistake has a
valid_until timestamp and an invalidated_by_commit reference, so an old
mistake auto-expires when its underlying cause is fixed.
Run:
engram mistakes -p $CLAUDE_PROJECT_DIR
The output lists active (still-valid) mistakes with confidence scores. When a mistake matches a query, engram surfaces it with ⚠️ at the top of the context packet, weighted 2.5× to ensure it gets attention.
Use this skill:
- Before refactoring a module: "are there known sharp edges here?"
- During debugging: "has this kind of error been seen before?"
- When onboarding to a new area of the codebase: "what's broken or fragile?"
To record a new mistake explicitly:
engram learn "Don't pass options.scope=user; SETTINGS_LOCAL takes precedence." -p $CLAUDE_PROJECT_DIR
Example invocations
User: "I'm about to refactor the rate limiter — anything I should know?"
You: Run engram mistakes -p $CLAUDE_PROJECT_DIR. Filter mentally for entries related to "rate", "limit", "mutex", or the file paths the user mentions. Surface the matches with their confidence scores: "engram has 3 active mistakes near this code, and one of them flagged this exact module:"
User: "Why does this test keep flaking?"
You: Run engram mistakes -p $CLAUDE_PROJECT_DIR. Look for entries about flakiness, timing, race conditions, or the test file's name. If a related mistake exists, quote it verbatim — chances are someone already debugged this.
User: "We just fixed a race condition in the queue worker. Remember it for next time."
You: Run engram learn "Queue worker had a race condition: don't read state.queue inside the await; snapshot it first" -p $CLAUDE_PROJECT_DIR. Confirm to the user that the mistake is recorded and will surface with ⚠️ on future Edits to that file.
User: "Has anyone fixed this kind of bug before?"
You: Run engram mistakes -p $CLAUDE_PROJECT_DIR. The graph carries 2.5x relevance boost on matching results, so if a similar fix exists, it surfaces near the top.
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.
- 12d ago First seen · 55 lines · 46 tokens per session scan A 45797dab6bf9
mistakes is a skill published in the GitHub repository Republicofhaitigoodstory6175/engram (1 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 726 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mistakes, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
handoff
Create, validate, list, and load local Portable Handoff capsules for context transfer, continuing work in a new chat, compacting current work, or loading prior work. Use whenever the user asks for a handoff, context transfer, continuation briefing, or portable work-state summary.
institutional-memory-distill
Distill decisions, reasoning, and rejected alternatives from PRs, design docs, and postmortems into the project's decisionledger, so ult-context-generate's trip-wire can surface institutional memory before new work quietly repeats settled ground. Do NOT use to query the ledger against new work or decide…
continuity-ledger
Create or update continuity ledger for state preservation across clears.
recall-reasoning
Search past reasoning for relevant decisions and approaches.
system-overview
Show users how Continuous Claude works - the opinionated setup with hooks, memory, and coordination.
remember
Store a learning, pattern, or decision in the memory system for future recall.