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/grpcer/ownmem/ownmem-initnpx skills add grpcer/ownmem --skill ownmem-initgit 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/ownmem-init)<a href="https://agentmods.dev/skills/grpcer/ownmem/ownmem-init"><img src="https://agentmods.dev/badge/skills/grpcer/ownmem/ownmem-init.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.00045 | $0.00359 |
| Opus 5 | $0.00023 | $0.00179 |
| Sonnet 5 | $0.00009 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
ownmem-init 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 yesterday.
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
95% identical to init — 2 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.
What it actually says
Set up OwnMem in this repository
OwnMem requires Node.js 20.6 or newer. Install the reviewed dependency, then generate the host adapters:
npm install --save-dev ownmem
npx ownmem init --locale auto --hosts claude,codex --layers dashboard --hook --command "npx ownmem"
Adjust the flags before running:
--hosts: any comma-separated combination ofclaude,codex,cursor,gemini, andgeneric— match the tools the team uses. Grok CLI reads the Codex adapter (.agents/skills/ownmemandAGENTS.md).--layers:core,gates,compiler, ordashboard—dashboardadds the local Web console.- Drop
--hookif the team does not want the Claude Code PreToolUse recall guard.
Initialization creates .ownmem/ plus bounded ownmem-generated blocks in the
host instructions, and preserves every line outside those boundaries. Verify:
npx ownmem init --check
npx ownmem audit
The npm package is the engine. This plugin is an optional shortcut and does not auto-update on every host. After a version bump (for example a Dependabot pull request):
npx ownmem init --update && npx ownmem init --check && npx ownmem audit
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.
- yesterday Changed · +4 lines e794a824685b
- 5d ago First seen · 35 lines · 45 tokens per session scan A 9a1736992a8a
ownmem-init is a skill published in the GitHub repository grpcer/ownmem (244 stars, last pushed yesterday), licensed Apache-2.0. It adds 45 tokens to every session and 359 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to init, differing in 2 lines, and is treated as a copy.
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.
memstate-ai
Persistent, versioned memory for AI agents via Memstate AI. Alternative to the Memstate MCP plugin — use for storing facts, recalling memory, managing projects, and semantic search of agent summaries. Supports Markdown ingestion and direct keypath = value assignment. Requires MEMSTATEAPIKEY.
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.