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-entitiesgit 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-entities)<a href="https://agentmods.dev/skills/joshuaswarren/remnic/remnic-entities"><img src="https://agentmods.dev/badge/skills/joshuaswarren/remnic/remnic-entities/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-entities"><img src="https://agentmods.dev/badge/skills/joshuaswarren/remnic/remnic-entities.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.00041 | $0.00523 |
| Opus 5 | $0.00020 | $0.00262 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
remnic-entities 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use when the user names a specific project, person, service, or concept and asks what is known about it. Entities are the structured graph view of memory — facts and relationships rather than free text.
Triggers:
- "Tell me about the entity …"
- "Look up …"
/remnic:entities <name>slash command invocation.- Any reference to a named thing that could have linked facts.
Inputs
name(required) — canonical entity name, ideally as the user wrote it.- Optional: entity type hint (project, person, service, tool).
Procedure
- Extract the entity name from the user's message. Preserve capitalization.
- Call
remnic_entity_getwith that name. - If found, present facts, relationships, and a last-updated timestamp in a compact block.
- If missing, say so and offer to create it via
remnic-rememberwith the user's permission. - If multiple candidates match, list them briefly and ask which the user meant.
Efficiency plan
- Do not fetch speculatively for every proper noun — only when the user asks or the task depends on it.
- Cache the entity payload within the current turn.
- Pair with
remnic-recallwhen unstructured context would round out the view.
Pitfalls and fixes
- Pitfall: Guessing entity names. Fix: Use the user's wording; disambiguate rather than inventing.
- Pitfall: Dumping the full payload. Fix: Summarize into facts, relations, last-updated.
- Pitfall: Treating missing entities as a bug. Fix: Missing just means the graph has not captured it yet.
Verification checklist
-
remnic_entity_getwas called with a user-supplied or user-confirmed name. - Output shows facts, relationships, and timestamps in a compact view.
- Missing entities are acknowledged plainly with an offer to create.
- Canonical
remnic_entity_getwas used over legacyengram_entity_get.
Tool names: canonical name is
remnic_entity_get. The legacyengram_entity_getalias 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 · 41 tokens per session scan A 493c187eedb5
remnic-entities is a skill published in the GitHub repository joshuaswarren/remnic (198 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 523 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.