Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add memseekai/memseek/plugin install memseek-memoryWrote 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/memseekai/memseek/memseek-status)<a href="https://agentmods.dev/skills/memseekai/memseek/memseek-status"><img src="https://agentmods.dev/badge/skills/memseekai/memseek/memseek-status/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/memseekai/memseek/memseek-status"><img src="https://agentmods.dev/badge/skills/memseekai/memseek/memseek-status.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.00024 | $0.00214 |
| Opus 5 | $0.00012 | $0.00107 |
| Sonnet 5 | $0.00005 | $0.00043 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
memseek-status 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 10d 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
Check Memseek status
Run the plugin's read-only diagnostic from the current project:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/memseek_doctor.py" status
Explain any failed field and its precise remedy. In particular:
- missing workspace key: reconfigure the plugin and enter the sensitive key supplied by the Memseek administrator, then start a new session.
- unhealthy or unreachable: start or repair the Memseek API/database.
- missing recommended tools: publish and select the compatible
[email protected]package, or an equivalent package exposing the documented contract. - pending writes: run the doctor with
flushafter connectivity returns. - quarantined writes: inspect the JSON envelope under the reported state directory's
failed/directory; it failed validation and is retained for diagnosis.
Never print or request the API key itself.
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.
- 10d ago First seen · 26 lines · 24 tokens per session scan A 6191711dc5b5
memseek-status is a skill published in the GitHub repository memseekai/memseek (7 stars, last pushed 15d ago), licensed Apache-2.0. It adds 24 tokens to every session and 214 once invoked, about $0.0001 per session on Opus 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
honcho-cli
Inspect and debug Honcho workspaces via the honcho CLI. Use when investigating peer representations, memory state, session context, or dialectic quality — any task that requires introspection of a Honcho deployment, including verifying that a recall/record memory loop is actually working.
troubleshooting
Diagnoses and repairs core-memory-kit itself when the memory system is broken — the per-failure-code repair book. Fire whenever a "⚠ [core-memory-kit]" whisper appears on the prompt (it names the failure and points here), or when the user reports a kit symptom however they phrase it: memory is not being saved, nothing…
atomicmemory
Persistent semantic memory across Claude Code sessions — user preferences, project context, prior decisions, codebase facts. Call memorysearch before answering questions that reference past work. Call memoryingest after the user shares durable facts.
atomicmemory-cli
Use the installed AtomicMemory CLI for memory search, ingestion, packaging, diagnostics, and agent-safe JSON output.
openmemory
Manage persistent memory via OpenMemory MCP. TRIGGER when: user says "remember this", "save to memory", "store this", "recall", "what do you remember about", "check memory", "forget this", "delete memory", "clean up memory", or when agent forms a stable conclusion worth persisting. DO NOT TRIGGER when: user refers to…
recall-before-claim
Forces a memorysearch before the agent sends a message containing a factual assertion that has not yet been grounded this turn. Closes the citation-rate gap from 40% to 90%+.