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 xpajonx/openempiric --skill remembergit clone --depth 1 https://github.com/xpajonx/openempiricWrote 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/xpajonx/openempiric/remember)<a href="https://agentmods.dev/skills/xpajonx/openempiric/remember"><img src="https://agentmods.dev/badge/skills/xpajonx/openempiric/remember/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/xpajonx/openempiric/remember"><img src="https://agentmods.dev/badge/skills/xpajonx/openempiric/remember.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.01183 |
| Opus 5.5 | $0.00024 | $0.00473 |
| Sonnet 5.5 | $0.00012 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
remember 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remember
This skill maps natural-language "remember" requests to the correct OpenEmpiric OEM MCP tool call.
OEM tools: knowledge_preflight, knowledge_session_start, knowledge_read, knowledge_search, knowledge_source_search, knowledge_source_read, knowledge_reflect, knowledge_session_end, knowledge_health_check, oem_checkpoint_create, oem_checkpoint_list, oem_checkpoint_restore, oem_todo_read, oem_todo_write, oem_todo_advance, knowledge_get_events.
Routing Table
Match the user's phrasing to the action below.
| When user says... | Do this |
|---|---|
| "remember" (start of session / standalone) | knowledge_session_start + knowledge_read(scope="recent") + knowledge_read(scope="project") + oem_checkpoint_list — surface the latest checkpoint, active work item, recent successes and failures. |
| "remember where we left off" | oem_checkpoint_list (latest checkpoint + active_work_item) + knowledge_read(scope="recent") + knowledge_read(scope="project") |
| "remember what we tried" / "remember failures" | knowledge_search("failure") + knowledge_read(scope="recent") — filter to failures. |
| "remember decisions about X" | knowledge_search("<X>") + oem_todo_read — search both concept memory and open tasks. |
| "remember the workflow for X" | knowledge_search("<X>") scoped to workflow/convention/decision memory. Also check directives/ if it exists. |
| "remember this" + fact | knowledge_reflect with structured events `[{event_type:"decision" |
| "remember this for next time" + observation | knowledge_reflect with events + oem_checkpoint_create to snapshot the current working set. |
| "restore checkpoint " | oem_checkpoint_restore(target="<id>") where <id> is the name_id from checkpoint list. |
| "list checkpoints" | oem_checkpoint_list |
| "what's my todo" / "what's next" | oem_todo_read |
| "add todo" + item | oem_todo_write to append the item. |
| "mark todo done" / "advance" | oem_todo_advance(item_id="<uuid>") |
| "remember" (end of session / finishing) | knowledge_reflect (summarize decisions+outcomes) + oem_checkpoint_create + knowledge_session_end |
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 · 85 lines · 59 tokens per session scan A 40a432ec89ea
remember is a skill published in the GitHub repository xpajonx/openempiric (10 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 1,183 once invoked, about $0.0002 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
audit-knowledge
Scan Antigravity conversation transcript + artifact directory for extractable knowledge. Use when user asks for 'knowledge audit', 'audit knowledge', 'check for extractable knowledge', 'scan transcript', or at session start when audit cadence is exceeded.
handoff
Generate a passoff package so the next reader can pick up cleanly — future-you in a new session (typically when context is high) or a coworker. Default + auto modes emit a paste-ready next-session opener plus PROGRESS / CLAUDE / memory updates, commit, and /extract; brief emits an 80-150 word coworker brief (no file…
audit-share
Internal facet of the audit family — invoke via '/audit share'. Batch-reviews personal knowledge for promotion to the team-shared project-knowledge/ tier; per-item opt-in, requires the shared-knowledge config.
wrapup
Close out a session cleanly when the work is done — no passoff intended. Reviews session work, updates PROGRESS.md / CLAUDE.md / memory, commits changes, captures session knowledge via /extract, and confirms everything is wrapped up, captured, and documented. Use when the task is complete and nothing needs to carry…
context
Load relevant knowledge by topic. Queries the tag index and presents matching promoted files for selective loading into context. Use when user says '/context stripe', '/context api pagination', '/context ss', 'load knowledge about...', 'what do we know about...'. (Code port — ADR-094.).
intake
Capture knowledge from outside the conversation. A single URL or text snippet is clipped whole to intake/clippings/; files/directories/globs are bulk-scanned into the backlogs; extract {source} decomposes a source into backlog entries; doc {source} captures a structured 5-section reflection…