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-remembergit 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-remember)<a href="https://agentmods.dev/skills/scottrbk/forgetful/forgetful-remember"><img src="https://agentmods.dev/badge/skills/scottrbk/forgetful/forgetful-remember/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-remember"><img src="https://agentmods.dev/badge/skills/scottrbk/forgetful/forgetful-remember.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.00071 | $0.01447 |
| Opus 5.5 | $0.00028 | $0.00579 |
| Sonnet 5.5 | $0.00014 | $0.00289 |
| Haiku 4.5 | $0.00007 | $0.00145 |
Grade A, and why
forgetful-remember 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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remembering knowledge in Forgetful
Capture is a sequence, not a single call: route the content to the right store, ground it in a project, check what already exists, then create atomically and link. Removal and rewriting happen by supersession only — a memory does not become less true because it hasn't been queried lately.
Invoking operations
Operations are named by registry name (query_memory, create_memory, ...). Invoke via
whichever surface this agent has:
- MCP:
execute_forgetful_tool(tool_name="create_memory", arguments={...}) - CLI:
forgetful call create_memory --args '{"title": "..."}' --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 — Route the type
| The content is... | Store as | Where |
|---|---|---|
| A single fact, decision, or preference | Memory | this skill, step 4 |
| Detailed analysis or a guide (>300 words) | Document + entry memories | this skill, step 4 |
| Reusable code | Code artifact | this skill, step 4 |
| A person, org, device, product, component | Entity | forgetful-entities |
| Step-by-step procedural knowledge | Skill | forgetful-procedures |
| Binary content (image, PDF, asset) | File | forgetful-files |
| A goal decomposing into steps / a work item | Plan / Task | feature-flagged; check discovery |
Done when: exactly one type is chosen, and routed-away types are handled by their skill.
Step 2 — Resolve the project
Every write needs a deliberate project decision. Derive the candidate from the repo:
git remote get-url origin → owner/repo → list_projects with repo_name. When no
project matches, create one or ask the user; when several could apply, ask.
Done when: a real project_id is confirmed — discovered or user-chosen, never assumed.
Step 3 — Query before create
Search for overlapping knowledge using the candidate's own essence as the query
(query_memory with query and query_context). Classify every relevant hit:
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.
- 3d ago Changed · +4 lines 69d8e71fc2e3
- 4d ago Changed · +8 lines fdf0917cb42d
- 1mo ago Changed ffaa1bf17c2f
- 1mo ago First seen · 123 lines · 71 tokens per session scan A 1cffd996b178
forgetful-remember is a skill published in the GitHub repository ScottRBK/forgetful (340 stars, last pushed 2d ago), licensed MIT. It adds 71 tokens to every session and 1,447 once invoked, about $0.0003 per session on Opus 5.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
core
This skill should be used when the user says "capture memory", "save to memory", "remember this", or trigger phrases like: "I've decided", "let's use", "we're going with", "I learned", "turns out", "TIL", "discovered", "I'm stuck", "blocked by", "always use", "never do", "convention is". Also triggers on recall…
format
MIF (Modeled Information Format) 1.4.2 Level 3 memory templates and formatting guidelines.
custodian
Memory system custodian for health checks, validation, and maintenance. Trigger phrases: "check memory health", "validate memories", "fix broken links", "update decay", "relocate memories", "audit memories", "memory maintenance", "custodian", "memory health".
ontology
Ontology-based entity discovery and validation for mnemonic memories. Define custom namespaces, entity types, traits, and relationships. Triggers: "entity discovery", "validate ontology", "define namespaces", "resolve entity references", "list ontologies", "show namespaces", "entity types", "entity relationships"…
blackboard
Cross-session handoff, persistent context via blackboard, and agent coordination patterns.
search
This skill should be used when the user says "search memories", "find in memories", "grep mnemonic", "look for memory", "deep search", "synthesize knowledge", or asks questions like "what do we know about X". Provides progressive disclosure and enhanced iterative search with synthesis.