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/miguelmedeiros/unforgit/unforgit-memorynpx skills add MiguelMedeiros/unforgit --skill unforgit-memorygit clone --depth 1 https://github.com/MiguelMedeiros/unforgitWrote 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/miguelmedeiros/unforgit/unforgit-memory)<a href="https://agentmods.dev/skills/miguelmedeiros/unforgit/unforgit-memory"><img src="https://agentmods.dev/badge/skills/miguelmedeiros/unforgit/unforgit-memory.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.00027 | $0.00573 |
| Opus 5 | $0.00014 | $0.00287 |
| Sonnet 5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
unforgit-memory 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 4d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unforgit Memory
Use this skill whenever work can benefit from durable project memory or when the user asks you to remember, recall, curate, or inspect repository knowledge.
Core workflow
- Recall first for substantive work. At the start of non-trivial coding, planning, debugging, release, or review work, call
unforgit_recallwith a query based on the user's request and the repository area being touched. - Use recalled context. Apply prior decisions, conventions, gotchas, and playbooks before changing code or proposing a plan.
- Save durable context promptly. When a stable decision, convention, gotcha, bug pattern, workaround, API contract, or reusable procedure emerges, call
unforgit_addwith concise self-contained text. - Curate when memory quality matters. Use
unforgit_health,unforgit_sync_status,unforgit_find_similar,unforgit_consolidate, andunforgit_curatewhen diagnosing memory quality, duplicates, sync, or stale notes.
What to save
semantic: stable facts, architectural decisions, conventions, API contracts.procedural: repeatable workflows, release/deploy playbooks, troubleshooting steps.episodic: notable bugs, gotchas, one-off observations that may prevent future mistakes.
What not to save
- Do not save secrets, tokens, passwords, API keys, private credentials, or sensitive environment values.
- Do not save temporary progress, task checklists, transient logs, command output dumps, PR numbers, commit SHAs, or facts likely to be stale soon.
- Do not save obvious information already documented in the repository unless the memory captures a decision or gotcha not obvious from the code.
Writing guidelines
- Write memory text in English unless the repository explicitly standardizes another language.
- Keep each memory concise but self-contained.
- Use tags such as
auth,api,deploy,bug,gotcha,decision, or package/module names. - Prefer repository-scoped Unforgit memory over global assistant memory for project-specific knowledge.
- If a memory may duplicate an existing one, search first and consolidate rather than creating noise.
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.
- 4d ago First seen · 43 lines · 27 tokens per session scan A 1b52d6e765f9
unforgit-memory is a skill published in the GitHub repository MiguelMedeiros/unforgit (9 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 573 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-31.
Other skills, from other repositories
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
argon-memory
Use an Argon Memory MCP server for durable project context, evidence-grounded retrieval, artifacts, work closeout, and conflict-aware memory.
exomem
Use when working with Exomem — your personal knowledge base (a markdown vault, Obsidian optional, of raw sources, compiled research notes, insights, failures, patterns, experiments, production-logs, typed entities, and Evidence artifacts). Triggers whenever you name Exomem (the connector/MCP you talk to) or want to…
agent-recall-trail
Recall and maintain one Agent's private, sourced experience together with human-reviewed shared ART Knowledge Editions. Use when prior decisions, procedures, project facts, user preferences, earlier failures, or reusable conclusions may affect the current task, and when the user asks to remember, retrieve, correct, or…
art-recall
Use Agent Recall Trail through its bound MCP tools when prior coding-agent experience or reviewed shared knowledge could materially change a decision. Governs recall, capture, reading, feedback, and proposals without bypassing ART storage or human review.