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 ScottRBK/forgetful --skill forgetful-entitiesgit clone --depth 1 https://github.com/ScottRBK/forgetfulWrote 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/scottrbk/forgetful/forgetful-entities)<a href="https://agentmods.dev/skills/scottrbk/forgetful/forgetful-entities"><img src="https://agentmods.dev/badge/skills/scottrbk/forgetful/forgetful-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/scottrbk/forgetful/forgetful-entities"><img src="https://agentmods.dev/badge/skills/scottrbk/forgetful/forgetful-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.00080 | $0.00785 |
| Opus 5 | $0.00040 | $0.00392 |
| Sonnet 5 | $0.00016 | $0.00157 |
| Haiku 4.5 | $0.00008 | $0.00078 |
Grade A, and why
forgetful-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 9d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modelling entities in Forgetful
Entities are the graph's nouns. Model the thing once, then let knowledge accrue to it
through links — that is what makes get_entity_memories a useful reverse lookup later.
Invoking operations
Operations are named by registry name (create_entity, link_entity_to_memory, ...).
Invoke via whichever surface this agent has:
- MCP:
execute_forgetful_tool(tool_name="create_entity", arguments={...}) - CLI:
forgetful call create_entity --args '{"name": "..."}' --json
Get any operation's schema at runtime: how_to_use_forgetful_tool (MCP) or
forgetful tools info <operation> (CLI) — schemas are deliberately not repeated here.
Step 1 — Apply the litmus, then dedupe
Can you point at it? "Sarah Chen" is an entity; "Sarah is great at debugging async issues"
is a memory linked to her. The fact stays a memory (forgetful-remember); the thing it is
about becomes the entity.
Before creating, search_entities for the thing under its likely names — it matches both
name and aka. Set aka at creation time for any alternative names the thing goes by, so
a later dedupe search under a different name still finds it.
Done when: the thing either already exists (use it) or is confirmed new.
Step 2 — Create with a type
create_entity with a name and type: Organization, Individual, Team, Device, System, or
Other (custom_type required when Other). Stored Title-case; matched case-insensitively on
input. Check list_entities for the types already in use and match them — a graph where
servers are sometimes typed "Device" and sometimes "System" fragments reverse lookups.
Done when: the entity exists once, typed consistently with the existing graph.
Step 3 — Link knowledge and projects as they accrue
link_entity_to_memorywhenever a memory is about the entity — done at capture time, this is one line; done later, it is an archaeology project.link_entity_to_projectwhen the entity belongs to a project's world.
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.
- 9d ago First seen · 73 lines · 80 tokens per session scan A 54d376fad50f
forgetful-entities is a skill published in the GitHub repository ScottRBK/forgetful (299 stars, last pushed 7d ago), licensed MIT. It adds 80 tokens to every session and 785 once invoked, about $0.0004 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
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.
remnic-memory-workflow
Shared memory workflow for Claude Code agents connected to Remnic — recall before acting, observe during work, remember at the end. Trigger phrases include "what do you remember about", "save this for later", "any context from last time".
remnic-recall
Search Remnic memories by natural-language query. Trigger phrases include "what do you remember about", "recall anything on", "have we discussed".
remnic-remember
Store a durable memory in Remnic so every connected agent can recall it. Trigger phrases include "remember this", "save this for later", "add a note that".
remnic-search
Run a deep full-text search across every Remnic memory. Trigger phrases include "search memories for", "find anything about", "deep search".
remnic-status
Check the health of the Remnic daemon, stores, and connected clients. Trigger phrases include "is remnic running", "check memory status", "daemon health".