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 grpcer/ownmem --skill recallgit clone --depth 1 https://github.com/grpcer/ownmemWrote 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/grpcer/ownmem/recall)<a href="https://agentmods.dev/skills/grpcer/ownmem/recall"><img src="https://agentmods.dev/badge/skills/grpcer/ownmem/recall/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/grpcer/ownmem/recall"><img src="https://agentmods.dev/badge/skills/grpcer/ownmem/recall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 18 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 25 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 38 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 40 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 45 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 46 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 47 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 52 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00066 | $0.00559 |
| Opus 5.5 | $0.00026 | $0.00224 |
| Sonnet 5.5 | $0.00013 | $0.00112 |
| Haiku 4.5 | $0.00007 | $0.00056 |
Grade A, and why
recall 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 23d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ownmem — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OwnMem recall and daily use
OwnMem is this repository's local, deterministic memory. Recall runs offline — no model calls, no network, no query-time token cost — and every memory is plain Markdown inside the repository.
If the repository has no .ownmem/ directory, OwnMem is not installed here;
use the init skill from this plugin first.
Recall before changing code
npx ownmem recall -- "problem, path, or symbol"
For natural-language symptoms, pass two or three phrasings in one call and let the deterministic fusion rank them:
npx ownmem recall --multi -- "symptom in plain words" "root-cause term" "english symbol"
Recall answers in one of three tiers, and reading them as the same thing is the one mistake that undoes the design:
- content — the memory's own text. It passed every gate; use it, then verify against live code, because a memory records what was true when it was written.
- pointers — up to three titles with the command that opens each one. This is not a short answer. Open the topic before you rely on anything in it.
- abstain — nothing is written down about this, and the envelope says which gate refused. Not a search failure to retry with different words.
Do not implement memory logic here
This skill only routes to the CLI. Flags, feedback names, and contracts belong to the installed package, not to this plugin. Host plugins are optional shortcuts and do not auto-update on every host, so a stale copy of this file must not teach a retired protocol.
Use npx ownmem --help and npx ownmem <command> --help for the current
surface. After a version bump, update the repository package and run
npx ownmem init --update.
Keep the memory healthy
npx ownmem audit
npx ownmem report --since 7d
npx ownmem dashboard --open
Write a new memory only for lessons that reading the code cannot recover —
upstream quirks, toolchain traps, timing races. Keep entries small and let
npx ownmem audit enforce the growth quota.
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.
- 23d ago Changed · +7 lines 49f1b89d81a5
- 1mo ago Changed · -31 lines afa21cdfaaa6
- 1mo ago First seen · 84 lines · 66 tokens per session scan A 2416d74f28c3
recall is a skill published in the GitHub repository grpcer/ownmem (429 stars, last pushed 2d ago), licensed Apache-2.0. It adds 66 tokens to every session and 559 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-30.
Other skills, from other repositories
ultramemory-snapshot
Compose and save a durable, wayback-grade session snapshot to UltraMemory. Use this whenever you are asked to write a session snapshot or rollup of the work just done — in particular when the UltraMemory capture hook nudges you to "Compose a session snapshot per the ultramemory-snapshot Skill rubric ... and save it…
setup
Guides Claude through first-time UltraMemory configuration after plugin install — API key, MCP server registration, test recall, and 401/403 troubleshooting.
ultramemory-recall-first
Load when the user asks about anything they may have told their AI before, wants persistent memory across tools, or asks what UltraMemory knows — recall from the user's connected UltraMemory connector first, write durable facts back, and never invent a memory.
krimto-write-fact
Use when the user asks you to remember something for later, save team knowledge, record a decision, or note a durable fact about the project, person, or team. Triggers on "remember that", "save this", "add to memory", "note for the team". Do not use for conversational context.
krimto-hierarchical-scope
Use when deciding what scope to store a fact at, or when reasoning about whether a fact applies to the current user. Krimto uses a user -> team -> org hierarchy with precedence rules. Triggers when scope selection is required.
krimto-recall-team
Use when starting a task, joining a conversation about a project, or before answering a question that needs team context. Triggers on "what do we know about X", "team's approach to Y", or before any domain-specific work.