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 wiolett-industries/marketplace --skill reconciling-memorygit clone --depth 1 https://github.com/wiolett-industries/marketplaceWrote 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/wiolett-industries/marketplace/reconciling-memory)<a href="https://agentmods.dev/skills/wiolett-industries/marketplace/reconciling-memory"><img src="https://agentmods.dev/badge/skills/wiolett-industries/marketplace/reconciling-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/wiolett-industries/marketplace/reconciling-memory"><img src="https://agentmods.dev/badge/skills/wiolett-industries/marketplace/reconciling-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.00043 | $0.00762 |
| Opus 5 | $0.00022 | $0.00381 |
| Sonnet 5 | $0.00009 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
reconciling-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 11d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconciling Agent Memory
Use this skill only for an explicit user request or an accepted overdue-reconciliation offer. It is a bounded maintenance pass, not routine startup work.
Scope And Consent
- Read
memory_reconciliation_statusfor the requested scope. Useprojectwith the absoluteworkspace_root; includeglobalonly if the user asked for it or the work is genuinely cross-project. - State which scope will be reconciled and what will be checked. If the user has not approved the maintenance pass, offer it and stop; a due timestamp is not authorization to mutate memory.
- Respect read-only/no-edits requests.
memory_reconciliation_record,memory_save, andmemory_updateare durable writes.
Bounded Pass
- Run one
memory_recapfor broad recovery. Use a focusedmemory_queryonly for a concrete suspected conflict or workflow. - Inspect the candidates for stale, duplicated, contradictory, overly broad, secret-bearing, or wrongly scoped content. Preserve ownership, negation, uncertainty, and project/global boundaries.
- Update an existing canonical memory when it can absorb the correction. Save only a truly new reusable lesson. Never invent facts from chat history or a recap.
- For an ordinary reconciliation, do not delete memories, prune graph edges, or re-embed content unless the user explicitly asks for that extra maintenance. Explain unresolved conflicts rather than silently choosing a side.
- After the scoped work is complete, call
memory_reconciliation_recordfor each reconciled scope with a concise secret-freesummary,reviewedcount when known,changesentries for every durable action, andunresolvedconflicts/follow-ups. Use empty arrays when there were none. For project memory, include the resulting.memory/maintenance/change in the intended repository diff.
Full Maintenance
An explicit request for full maintenance, or the agent-memory consolidate confirmation that names full maintenance, authorizes this additional bounded cleanup for the selected scope:
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.
- 11d ago First seen · 37 lines · 43 tokens per session scan A 0a24f94c5d14
reconciling-memory is a skill published in the GitHub repository wiolett-industries/marketplace (10 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 762 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…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.