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 SoliEstre/EstreGenesis --skill eg-memsyncgit clone --depth 1 https://github.com/SoliEstre/EstreGenesisWrote 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/soliestre/estregenesis/eg-memsync)<a href="https://agentmods.dev/skills/soliestre/estregenesis/eg-memsync"><img src="https://agentmods.dev/badge/skills/soliestre/estregenesis/eg-memsync.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.00093 | $0.01333 |
| Opus 5 | $0.00046 | $0.00666 |
| Sonnet 5 | $0.00019 | $0.00267 |
| Haiku 4.5 | $0.00009 | $0.00133 |
Grade A, and why
eg-memsync 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 8d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/eg-memsync (/egmem) — reconcile agent memory ↔ project docs
Agent memory and project docs drift apart in both directions, and each direction is a real failure mode. Memory absorbs corrections faster than docs do — so a doc keeps stating a policy that a dated memory has since revised, sometimes while citing that very memory file by name. And docs (plus the repo itself) move on while memory keeps stale state — a memory still "waiting" on a gate that was resolved dozens of releases ago, or an index whose one-line summaries no longer match the files they index. Either way the next session inherits a contradiction and has to guess. This skill is the periodic true-up.
0. Locate the two corpora
- Memory — the per-project agent memory store: on Claude Code, the project's auto-memory directory (
memory/*.mdplus its index file); otherwise the workspace'smemory/feedback_*.mdconvention or the harness equivalent. No memory store → nothing to reconcile. Say so and stop — do not invent one. - Docs — the project's governance surfaces:
AGENTS.md(the SSoT),.agent/rules.md(operational detail), and the per-tool bridge files (CLAUDE.mdand friends). A project not on the AGENTS.md pattern routes to/eg-migrationfirst; a project with no seed at all routes to/eg-bootstrap.
Read both corpora fully before judging anything — drift detection on a partial read produces false confidence.
1. Detect drift — five kinds
Sweep every memory file against every doc section (and the memory index against its own files):
- (a) memory supersedes doc — a doc states a policy that a dated memory has since revised. The strongest tell: the doc cites the memory file by name while carrying the pre-revision content.
- (b) dangling references — a doc cites a memory file, directory, or convention that does not exist (or no longer does); a memory wikilink points at a renamed or missing target; a placeholder link was never filled in.
- (c) memory-only durable policy — an operating rule (a restart procedure's required environment, a deploy-drift caveat, a content-tone standard, a routing rule) that lives only in memory with no doc surface. These are the promotion candidates.
- (d) duplicated content where one copy went stale — the same fact stated in both places with different values. The memory index counts: an index entry that summarizes an older revision of its own file is this kind.
- (e) outdated identifiers — versions, dates, paths, counts that one side visibly outgrew. Internal contradictions inside a single doc (two sections quoting two different versions of the same thing) count too.
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.
- 8d ago First seen · 48 lines · 93 tokens per session scan A 267d4c7df629
eg-memsync is a skill published in the GitHub repository SoliEstre/EstreGenesis (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 93 tokens to every session and 1,333 once invoked, about $0.0005 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
update-agent-context
This skill should be used to keep CLAUDE.md, AGENTS.md, and the skill files themselves compact, current, and internally consistent. It runs in three phases: Phase 1 performs a one-time structural refactor of CLAUDE.md using a Karpathy-inspired behavioral scaffold and derives AGENTS.md from it by stripping Claude…
watercooler-onboarding
Bootstrap Watercooler memory for a repository by inspecting local code, docs, CI, git history, and existing Watercooler threads, then writing a small set of durable, provenance-backed seed threads that future agents can query and extend. Use when entering a repo for the first time, seeding a repo with Watercooler…
recall
Recall project context or answer questions about history and decisions. Use before starting work, when investigating unfamiliar code, or asking "What was decided about X?" / "Why did we choose Y?".
wiki
Use this skill when querying workspace knowledge before tasks or running mandatory post-review ingest evaluation and conditional wiki ingestion. Self-learning loop for the workspace.
mem0-integration
Mem0 memory layer integration for AI agents. Implement persistent, semantic memory for long-term context retention and personalization.
moai-foundation-context
Manages context window optimization, session state persistence, and token budget allocation for multi-agent workflows. Use for token budget management, context limits, or session handoff across agents.