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 LucasSantana-Dev/sharekit --skill sync-memoriesgit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/sync-memories)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/sync-memories"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/sync-memories/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/lucassantana-dev/sharekit/sync-memories"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/sync-memories.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.00037 | $0.00837 |
| Opus 5.5 | $0.00015 | $0.00335 |
| Sonnet 5.5 | $0.00007 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00084 |
Grade B, and why
sync-memories scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat ~/.claude/projects/<slug>/memory/<name>.md | head -20 How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Memories — Session Knowledge Capture
Update persistent memory systems with session accomplishments so future sessions have accurate context.
When to use
- After completing a PR / feature / refactor session
- After a release (version bump, changelog, tag)
- After discovering important architecture or gotcha info
- When existing memories are stale (test counts, versions, READMEs outdated)
Workflow
1. Gather current state
git log --oneline -10
git diff --stat HEAD~3 2>/dev/null || git diff --stat HEAD
git branch --show-current
git status
# If JS/TS project:
node -p "require('./package.json').version" 2>/dev/null
npm test 2>&1 | grep -E "Tests:|Test Suites:" | tail -2
2. Pick the right memory system
| Tool present | Where memories live | Update via |
|---|---|---|
| Claude Code project memory | ~/.claude/projects/<slug>/memory/*.md |
direct file edit + MEMORY.md pointer line |
Serena MCP (.serena/) |
per-project memories | serena.write_memory(name, content) |
| claude-mem MCP | FTS5 DB | save_memory({project, title, text}) |
.agents/memory/<project>.md |
tracked in repo | append a ## Session YYYY-MM-DD block |
Use all that apply. They don't conflict; recall queries each separately.
3. Update — one fact per file
Each memory file holds one fact. Frontmatter required (see global CLAUDE.md). For project memories: type: project, link related notes with [[name]], and add a one-line pointer to MEMORY.md so the index loads it next session.
For Serena memories, standard categories:
project_overview— version, test count, recent PRs, open workarchitecture— boundaries, key filesgotchas— things that surprised you- one memory per logical accomplishment, not per file
4. Verify
# Spot-check the most-edited memory
cat ~/.claude/projects/<slug>/memory/<name>.md | head -20
# or
serena.read_memory("project_overview")
Check: version matches package.json, test count matches latest run, recent PRs listed.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 99 lines · 37 tokens per session scan B 8442abfa71b6
sync-memories is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 837 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
brain-ingest
The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…
save-learning
Saves user instructions as persistent learnings for future sessions. Use when the user says 'remember this', 'always do X', 'from now on', 'never do Y', or gives any instruction they want persisted across sessions. Proactively suggest when the user states a preference, convention, or rule they clearly want followed in…
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.
getnote-kb
A skill for reading and managing GetNote Brain, a knowledge-base service for books, customer records, team information, folders, notes, and subscribed creators or livestreams.