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 joshuaswarren/remnic --skill remnic-statusgit clone --depth 1 https://github.com/joshuaswarren/remnicWrote 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/joshuaswarren/remnic/remnic-status)<a href="https://agentmods.dev/skills/joshuaswarren/remnic/remnic-status"><img src="https://agentmods.dev/badge/skills/joshuaswarren/remnic/remnic-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/joshuaswarren/remnic/remnic-status"><img src="https://agentmods.dev/badge/skills/joshuaswarren/remnic/remnic-status.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.00037 | $0.00499 |
| Opus 5 | $0.00018 | $0.00249 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
remnic-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 12d 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
When to use
Use when the user asks whether Remnic is running, when recall or store calls start failing, or when diagnosing cross-agent memory issues from Claude Code.
Triggers:
- "Is Remnic running?"
- "Check memory status."
/remnic:statusslash command invocation.- Recall/store tools returned connection errors in this turn.
Inputs
- Optional: specific component to check (daemon, HTTP server, MCP server, store backend).
Procedure
- Check the Remnic health endpoint via the MCP bridge or run
remnic daemon statusin a shell. - Report, in a compact block:
- Daemon running state (PID if known).
- Listening port(s).
- Memory store path.
- Connected clients or plugins, if exposed.
- If the daemon is not running, suggest
remnic daemon startand mention the log path. - If recall/store tools were erroring earlier in the turn, correlate the health state with those errors in one sentence.
Efficiency plan
- One health call per turn is enough; do not poll.
- Skip the check for trivially local tasks.
- Reuse the health payload for downstream troubleshooting within the same turn.
Pitfalls and fixes
- Pitfall: Running
remnic daemon statuson a host where the daemon lives in a container. Fix: Prefer the MCP health endpoint, or run the CLI inside the container. - Pitfall: Reporting "down" from a single failed tool call. Fix: Confirm with the health endpoint before claiming an outage.
- Pitfall: Forgetting the log path. Fix: Always include a pointer to logs on failure.
Verification checklist
- Health was checked via the endpoint or CLI, not guessed.
- Daemon state, port, store path, and clients were reported concisely.
- If unhealthy, the user got a concrete next step.
- Canonical
remnic daemonwording was used over legacyengram daemonwhere the CLI has been renamed.
CLI names: canonical CLI is
remnic daemon. The legacyengram daemoninvocation remains accepted during v1.x.
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.
- 12d ago First seen · 52 lines · 37 tokens per session scan A a3af05148fd5
remnic-status is a skill published in the GitHub repository joshuaswarren/remnic (198 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 499 once invoked, about $0.0002 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-30.
Other skills, from other repositories
claude-memory
Access the persistent memory database (PostgreSQL claudememory) for long-term context across Claude Code sessions. Triggers on "what do I know about", "memory lookup", "recall", "memory db", "what did we decide about", "similar conversations", "lookup context", "/memory". Provides semantic search, SQL queries and the…
project-context-loader
Load relevant memory, decisions and contacts for the current project at the start of a session.
plur-create-engrams
Create or improve PLUR engrams from conversations, documents, decisions, observations, and explicit preferences. Use for memory extraction, engram authoring, or reviewing proposed memories, including global, scoped, pinned, retrieved, and provisional knowledge. Ordinary use of existing memories does not require this…
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
plur-session-end
Extract durable learnings at the end of a session. Saves corrections, preferences, and codebase patterns as engrams — nothing ephemeral, nothing sensitive.
plur-memory
Your memory stays on your machine. No cloud, no tracking, no API key. PLUR makes your OpenClaw remember — and shares that memory with every other tool you use.