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 mitodl/agent-kit --skill witan-memorygit clone --depth 1 https://github.com/mitodl/agent-kitWrote 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/mitodl/agent-kit/witan-memory)<a href="https://agentmods.dev/skills/mitodl/agent-kit/witan-memory"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/witan-memory/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/mitodl/agent-kit/witan-memory"><img src="https://agentmods.dev/badge/skills/mitodl/agent-kit/witan-memory.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.00112 | $0.02455 |
| Opus 5.5 | $0.00045 | $0.00982 |
| Sonnet 5.5 | $0.00022 | $0.00491 |
| Haiku 4.5 | $0.00011 | $0.00246 |
Grade A, and why
witan-memory 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 19d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Memory
The team's shared knowledge graph stores four kinds of memories, all
backed by Omnigraph and accessible via the witan MCP server.
The repo is auto-detected from .git/config — you rarely need to pass it
explicitly.
This graph vs. CLAUDE.md / AGENTS.md
CLAUDE.md / AGENTS.md hold static, human-committed project instructions
that load into every session automatically. This graph holds facts, patterns,
and lessons you accrue and query on demand, shared across agents and repos.
Don't duplicate committed CLAUDE.md content into the graph; use the graph for
what you learn while working that isn't already written down.
This graph vs. your built-in / session memory
Your coding agent also has a private, on-disk built-in/session memory (e.g.
Claude Code's memory/ files). That store is local to one machine and one user;
witan is shared across the team, synced, and queryable by every agent and
repo. They overlap in purpose, so choose deliberately:
- Store in witan anything another agent, a future session, or a teammate would benefit from: project facts, reusable patterns, lessons from a mistake, decisions and their rationale, hand-off context — especially when it's tied to a repo, code symbol, task, or project. This is the default for engineering knowledge worth keeping.
- Keep in built-in/session memory only what is private or non-shareable: machine-local paths, personal scratch notes, harness/tooling preferences, or ephemeral state for the task in front of you right now.
Rule of thumb: if it's durable AND shareable, it goes in witan. When in doubt, prefer witan — a teammate finding your lesson is the entire point; a note stranded in one machine's session memory helps no one else. If you catch yourself about to write an engineering fact, pattern, or lesson to local session memory, store it here instead (or as well, if the harness mandates a local write).
When to Use Each Tool
recall — load context (the default read)
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.
- 19d ago Changed · +1 lines 1821f9b481d8
- 25d ago Changed · +1 lines c8af0efca34c
- 1mo ago Changed · +13 lines 3f0c5a5a389a
- 1mo ago First seen · 224 lines · 112 tokens per session scan A 408337eace21
witan-memory is a skill published in the GitHub repository mitodl/agent-kit (5 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 112 tokens to every session and 2,455 once invoked, about $0.0004 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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.