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 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/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/miguelmedeiros/unforgit/unforgit-memory"><img src="https://agentmods.dev/badge/skills/miguelmedeiros/unforgit/unforgit-memory.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00573 |
| Opus 5.5 | $0.00011 | $0.00229 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 43 lines · 27 tokens per session scan A 1b52d6e765f9
unforgit-memory is a skill published in the GitHub repository MiguelMedeiros/unforgit (11 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 573 once invoked, about $0.0001 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-31.
Other skills, from other repositories
init
Turn on Rekal memory in the current repository by running rekal init. Use when the user asks to initialize or set up Rekal here, or when a rekal command reported the repository is not initialized. Once per repository. Do not offer this merely because a repo lacks a .rekal/ store — most repos do not want one.
loredex-sync
Commit local dex changes, pull teammates' notes, push yours — the team-sharing loop for a git-backed dex. Use when the user says "sync the dex", "push my notes", "pull the latest dex", or after finishing work another team should see.
awiki-save
Save content from the current conversation to the Agent Wiki. Use when research, decisions, or valuable findings should be preserved.
awiki-ingest
Ingest an existing file into the Agent Wiki. Use when the user has a file they want to add to the knowledge base.
syncing-memory-filesystem
Diagnose and repair MemFS repository setup, remote sync, authentication failures, optional backup remotes, or merge/rebase conflicts. Do not load for routine memory reads or edits.
openlore
Query and publish to an OpenLore knowledge repository over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.