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 U4CSolutions/MidMem --skill midmem-pattern-capturegit clone --depth 1 https://github.com/U4CSolutions/MidMemWrote 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/u4csolutions/midmem/midmem-pattern-capture)<a href="https://agentmods.dev/skills/u4csolutions/midmem/midmem-pattern-capture"><img src="https://agentmods.dev/badge/skills/u4csolutions/midmem/midmem-pattern-capture/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/u4csolutions/midmem/midmem-pattern-capture"><img src="https://agentmods.dev/badge/skills/u4csolutions/midmem/midmem-pattern-capture.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.00070 | $0.00472 |
| Opus 5.5 | $0.00028 | $0.00189 |
| Sonnet 5.5 | $0.00014 | $0.00094 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
midmem-pattern-capture 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.
What it actually says
Pattern capture — record what builds prove
Capture packs make MidMem domain-extensible as data: a pack registers entry types (with a
persistence tier + memory function + graph edge), categorizer rules and an edge vocabulary.
The shipped coding-patterns pack covers: pattern, scaffold, anti-pattern, recipe
(all procedural-function, memory-tier).
When to capture
- At the moment of proof, not from memory: a card/QA gate just passed using an approach worth reusing → record it NOW with its evidence link (commit hash, repo, card id).
- A debugging approach failed for a reproducible reason →
anti-patternwith the failure as evidence. Dead ends prevent repeats; that is their entire value. - The same scaffold got copied into a second project →
scaffold, evidence both repos.
How
midmem pattern --type pattern --title "<short name>" \
--context "<where this applies>" --problem "<what it solves>" \
--solution "<the approach>" --evidence "<repo@hash;card-id>" [--scope shared]
(MCP: record_pattern; list registered types with midmem packs.)
Rules
- Evidence is required in spirit: a pattern without a commit/repo/run reference is an opinion. Link the proof.
- Never hand-promote. Patterns start at memory tier; retrieval renewals during later builds are what earn wisdom. A "best practice" nobody re-uses should decay.
- Anti-patterns are captures, not shame: record the failure mode plainly; the dead-end demotion in retrieval surfaces them as warnings automatically.
- New domains = new pack JSON (entry types + rules + edges), registered via
MIDMEM_CAPTURE_PACKS— never a core code change. Packs cannot redefine core types.
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 · 37 lines · 70 tokens per session scan A fdf7022d30f3
midmem-pattern-capture is a skill published in the GitHub repository U4CSolutions/MidMem (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 70 tokens to every session and 472 once invoked, about $0.0003 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-31.
Other skills, from other repositories
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…
braindb
Memory recall and save. Use at every conversation start and whenever the user shares personal information, expertise, project context, preferences, or decisions worth remembering long-term.
braindb-agent
Persistent memory across sessions via the BrainDB agent. Use at conversation start and whenever you need to recall what you know about the user or save new information to long-term memory.
braindb-custom-profile
How to author a BrainDB custom profile — prompt add/replace fragments and an optional keyless ingestor — that shapes wiki naming/structure and feeds a custom ingestion source, with zero effect on defaults when inactive.
remnic-memory-workflow
Shared memory workflow for Claude Code agents connected to Remnic — recall before acting, observe during work, remember at the end. Trigger phrases include "what do you remember about", "save this for later", "any context from last time".