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 agentmods add skills/nxcoreai/everroom/entity-identitynpx skills add NxcoreAI/EverRoom --skill entity-identitygit clone --depth 1 https://github.com/NxcoreAI/EverRoomWrote 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/nxcoreai/everroom/entity-identity)<a href="https://agentmods.dev/skills/nxcoreai/everroom/entity-identity"><img src="https://agentmods.dev/badge/skills/nxcoreai/everroom/entity-identity.svg" alt="Measured on agentmods" 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.00018 | $0.00112 |
| Opus 5 | $0.00009 | $0.00056 |
| Sonnet 5 | $0.00004 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
entity-identity 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 7d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 7d ago First seen · 11 lines · 18 tokens per session scan A 4a0e4e5fb33b
entity-identity is a skill published in the GitHub repository NxcoreAI/EverRoom (837 stars, last pushed yesterday), with no licence file. It adds 18 tokens to every session and 112 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-30.
Other skills, from other repositories
wegent-knowledge
Knowledge base management and search tools for Wegent. Provides capabilities to list, create, update, and search knowledge bases and documents using RAG retrieval. Use this skill when the user wants to manage knowledge bases, documents, or search for information programmatically.
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
openlore
Query and publish to an OpenLore knowledge base over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.
openlore-housekeeping
Audit and maintain a shared OpenLore knowledge base. Use on a schedule or on request to find stale docs, broken links, unreviewed inbox items, and missing skill coverage, then publish an audit report.
continuous-learning
Use when a mistake, correction, or surprise taught the workspace something that must stick — a retro or postmortem, the same agent error corrected twice, a resolved bug's root cause, scattered notes-to-self — and route that lesson to the durable surface that fires next time. NOT a forward choice with alternatives…
Wikimate Query
This skill should be used when the user asks to find, search, recall, or summarize from their own previously-organized notes/wiki — e.g. "내 볼트에서 찾아줘", "위키에서 물어봐/검색해줘", "전에 정리한 요약해줘", "내가 저장한 뭐였지", "search my notes/vault for ", "what did I save about ", or to connect/synthesize across multiple notes — "내 노트들로 설명/비교/관계…