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/mubit-ai/claude-plugins/forgetnpx skills add mubit-ai/claude-plugins --skill forgetgit clone --depth 1 https://github.com/mubit-ai/claude-pluginsWrote 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/mubit-ai/claude-plugins/forget)<a href="https://agentmods.dev/skills/mubit-ai/claude-plugins/forget"><img src="https://agentmods.dev/badge/skills/mubit-ai/claude-plugins/forget.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 | $0.00034 | $0.00576 |
| Opus 5 | $0.00017 | $0.00288 |
| Sonnet 5 | $0.00007 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
forget 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 5d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Call mubit_forget with lesson_id — the reference_id cited in recalled context, or the
lesson_id reported by /mubit-memory:reflect. Confirm the id and the text with the user
before you call it; there is no dry run.
Pass lesson_id and nothing else. The same tool accepts session_id, and that argument
deletes the entire run — every capture, trace, and lesson in it — not one entry. Never
send it unless the user has asked for exactly that, in those words.
There is also no "mark superseded" operation: nothing flags an entry as replaced. Superseding is done the way described below — write the corrected lesson, and down-weight the old one so retrieval stops preferring it.
Read this before deleting
Deletion is not undoable. There is no tombstone to restore from, no recycle bin, and the entry's accumulated reinforcement history — every outcome that ever credited or blamed it — goes with it.
A lesson that is merely wrong is usually better handled with mubit_outcome and a negative
signal:
mubit_outcome reference_id=<the lesson> outcome=failure signal=-1
rationale="<why it was wrong, in one sentence>"
The promotion pipeline acts on that. The lesson's confidence drops, it stops surfacing near the top of recall, and — this is the part deletion cannot do — the reason it was wrong is now part of the record. A deleted lesson teaches the system nothing. A down-weighted one teaches it something, and the correction survives to shape what gets promoted next.
When deletion is actually right
- The entry should never have existed: a secret, a customer name, a path from someone else's machine that slipped past redaction.
- It is factually about a different project and will keep polluting recall here.
- The user asks for it directly, after being told it cannot be undone.
Everything else — a lesson that is outdated, over-general, or true-but-annoying — is a
mubit_outcome with a negative signal, or a fresh, better-worded lesson via
/mubit-memory:remember that supersedes it in retrieval. Reach for deletion last, not first.
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.
- 5d ago First seen · 49 lines · 34 tokens per session scan A 99986c81e5fa
forget is a skill published in the GitHub repository mubit-ai/claude-plugins (13 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 576 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…