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 fthsrbst/mnema --skill memory-hygienegit clone --depth 1 https://github.com/fthsrbst/mnemaWrote 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/fthsrbst/mnema/memory-hygiene)<a href="https://agentmods.dev/skills/fthsrbst/mnema/memory-hygiene"><img src="https://agentmods.dev/badge/skills/fthsrbst/mnema/memory-hygiene.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.1 | $0.00056 | $0.00898 |
| Opus 5 | $0.00028 | $0.00449 |
| Sonnet 5 | $0.00011 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
memory-hygiene 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 6d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bellek Hijyeni (Memory Hygiene)
Hub zamanla tekrar, eskimiş ve çelişkili kayıtlarla dolar. Hijyen araçları bu sorunları tespit eder ve çözer.
Hijyen Raporu
hygiene_report
{}
Dönen rapor:
duplicates— benzer/tekrar kayıtlar (aynı bilgi farklı wording)stale— uzun süredir erişilmemiş, düşük önem kayıtlarcontradictions—contradictsilişkisi olan ama ikisi de aktif kayıtlarsuggestions— önerilen aksiyonlar
Otomatik Temizlik
hygiene_run
{}
Yapılan işlemler:
- Eskileri arşivle: 90+ gün erişilmemiş, importance < 0.7 → importance 0.5'e düşür, "archived" tag ekle
- Çelişkileri işaretle:
contradictsilişkisi olan kayıtları raporla
Dikkat: Otomatik temizlik silmez, sadece arşivler. Silme kararı manuel verilmeli.
Manuel Müdahale
Tekrar Birleştirme
İki kayıt aynı bilgiyi içeriyorsa:
- İyi olanı seç (daha eksiksiz, daha güncel)
memory_updateile diğerinin bilgisini ekle- Kötü olanı
memory_deleteile sil
Çelişki Çözümü
İki kayıt çelişiyorsa:
- Hangisi doğru/güncel belirle
- Yanlış olanı sil VEYA
memory_updateile düzelt - Çelişki ilişkisini kaldır
Eskimiş Temizliği
stale listesindeki kayıtlar için:
- Hâlâ geçerli mi? → importance artır,
last_accessedgüncelle - Artık geçersiz mi? → sil
- Nadiren lazım mı? → arşivde bırak (importance 0.5)
Bilgi Sıkıştırma (Compaction)
compact_project
{ "project": "my-project", "mode": "sessions" }
Modlar:
sessions— son N oturum özetini tek "proje geçmişi" dokümanına sıkıştırdecisions— eski kararları karar-özet dokümanına birleştirdistill— tam sıkıştırma: oturumlar + kararlar + eski hafızalar → özet referans
Ne zaman sıkıştır:
- Proje çok uzun süredir aktif (50+ oturum)
- Bağlam çok büyüdü, recall yavaşladı
- Eski bilgiler artık detay değil, sadece özet yeterli
Periyodik Bakım Önerisi
| Sıklık | Aksiyon |
|---|---|
| Her oturum | Çelişki görürsen hemen düzelt |
| Haftalık | hygiene_report kontrol et |
| Aylık | hygiene_run + manuel tekrar birleştirme |
| Proje bazlı | 50+ oturumda compact_project |
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.
- 6d ago First seen · 89 lines · 56 tokens per session scan A 2f6bfff5d15f
memory-hygiene is a skill published in the GitHub repository fthsrbst/mnema (2 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 898 once invoked, about $0.0003 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
recall
Use Recall to search, inspect, continue, export, resume, or share indexed AI coding sessions. Trigger for project-history lookup, recent work from other agents, file history, unfinished-session continuation, and published session-page management.
reflect
Use Recall Reflect to review AI coding workflow history as a conversation-first timeline and discuss observed patterns before changing behavior. Trigger when the user asks to reflect on a project, review AI coding workflow, inspect workflow friction, discuss repeated corrections, review handoffs, or explore possible…
memorywhale
Query and write durable debugging memory recorded by MemoryWhale. Use when debugging a failure that may have happened before, when you need the exact error/flags/output from an earlier attempt, when the user asks "how did we fix this last time?", or once you've figured out why something failed / how a fix worked and…
daily-brief-loop
Use only when the user explicitly asks to run, sync, advance, or persist Mora's durable daily brief. Executes the once-per-day, human-checkpointed NO-SEND operator loop, performs configured source syncs, writes the dated artifact and run log, and advances the brief watermark.
any-mcp
Use when an agent needs to read, search, create, edit, organize, upload, or chat with Anytype through the bounded any-mcp server. Covers safe tool selection, exact identifier chaining, optional toolsets, common PKM workflows, and the narrow anyr fallbacks for chat subscriptions and rich chat blocks.
mora-recall
Retrieve the user's own history before answering questions about their people, projects, meetings, messages, decisions, commitments, or past work. Use for requests such as "what did we discuss", "what did I decide", "what do you know about", "catch me up", and "what changed".