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 debug-loggit 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/debug-log)<a href="https://agentmods.dev/skills/fthsrbst/mnema/debug-log"><img src="https://agentmods.dev/badge/skills/fthsrbst/mnema/debug-log/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/fthsrbst/mnema/debug-log"><img src="https://agentmods.dev/badge/skills/fthsrbst/mnema/debug-log.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.00072 | $0.00377 |
| Opus 5.5 | $0.00029 | $0.00151 |
| Sonnet 5.5 | $0.00014 | $0.00075 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
debug-log 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.
What it actually says
Debug Log
Zor çözülen her bug bir daha karşına çıkar — başka projede, başka cihazda, aylar sonra. Çözümü kaydet ki ikinci seferde dakikalar sürsün.
Ne zaman kaydet
- Kök nedeni bulmak 30+ dakika sürdüyse
- Hata mesajı yanıltıcıydıysa (asıl sorun başka yerdeydi)
- Ortama/versiyona özgü bir sorunsa (Windows path, Node sürümü, ARM, driver...)
- Aynı hataya daha önce de rastladığını fark ettiysen (→ kesin kaydet)
Format
memory_save ile, type=howto, tags=["debug", ]:
title: <hata mesajının/belirtinin aranabilir özeti>
body:
**Belirti:** ne görünüyordu (hata mesajı birebir — aranabilirlik için önemli)
**Yanıltıcı iz:** neyi sandık, neden yanlıştı (varsa)
**Kök neden:** asıl sorun
**Çözüm:** ne yapıldı (komut/kod ile)
**Ders:** bir dahaki sefere ilk nereye bakmalı
Önce ara
Yeni bir zorlu hatayla karşılaşınca kaydetmeden önce memory_search(<hata mesajı>) — belki geçmişteki sen çoktan çözmüş.
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 · 31 lines · 72 tokens per session scan A a63fed9b3351
debug-log is a skill published in the GitHub repository fthsrbst/mnema (2 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 377 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-31.
Other skills, from other repositories
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…
memorywhale-evidence
Use MemoryWhale debugging evidence when the user requests recall or a recurring failure may have relevant recorded history.
memorywhale-debugging
MemoryWhale debugging; compiler failures; terminal diagnostics.
sivtr-memory
Retrieve shared local work memory: terminal activity, AI conversation history, prior decisions, validation evidence, debugging trails, recaps, and handoff context. Use before asking the user to repeat local work context.
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…