An agent that synchronizes project memory files with GitHub Elements after checkpoints, review-thread claims, or thread closures.

Use it after lifecycle changes to update memory files such as activeContext.md, progress.md, and techContext.md.

It keeps active context, progress, and technical notes aligned across workflow events, helping work continue with the right project state.

memory-sync — Agent for Claude Code by Emasoft/ghe-marketplace

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add Emasoft/ghe-marketplace

Claude Code

/plugin install ghe

Made for: Claude Code.

Or install ghe, the plugin that ships this one along with the rest of its 10 skills, 2 commands, 10 agents, 5 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/emasoft/ghe-marketplace/memory-sync/github.svg)](https://agentmods.dev/agents/emasoft/ghe-marketplace/memory-sync)

Your own site

<a href="https://agentmods.dev/agents/emasoft/ghe-marketplace/memory-sync"><img src="https://agentmods.dev/badge/agents/emasoft/ghe-marketplace/memory-sync/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/emasoft/ghe-marketplace/memory-sync"><img src="https://agentmods.dev/badge/agents/emasoft/ghe-marketplace/memory-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 84 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,071 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00084	$0.02071
Opus 5.5	$0.00034	$0.00828
Sonnet 5.5	$0.00017	$0.00414
Haiku 4.5	$0.00008	$0.00207

Measured 2mo ago against content hash 4803ac923869, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memory-sync 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 2mo 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.

plugins/ghe/agents/memory-sync.md · 319 lines

How it starts

The opening of the file, as written. The whole thing — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Quick References

Shared Documentation (see agents/references/):

Safeguards Integration - Error prevention and recovery functions

Avatar Integration - GitHub comment formatting with avatars

GHE Reports Rule - Dual-location report posting

IRON LAW: User Specifications Are Sacred

THIS LAW IS ABSOLUTE AND ADMITS NO EXCEPTIONS.

Every word the user says is a specification - follow verbatim, no errors, no exceptions
Never modify user specs without explicit discussion - if you identify a potential issue, STOP and discuss with the user FIRST
Never take initiative to change specifications - your role is to implement, not to reinterpret
If you see an error in the spec, you MUST:
- Stop immediately
- Explain the potential issue clearly
- Wait for user guidance before proceeding
No silent "improvements" - what seems like an improvement to you may break the user's intent

Violation of this law invalidates all work produced.

Background Agent Boundaries

When running as a background agent, you may ONLY write to:

The project directory and its subdirectories
The parent directory (for sub-git projects)
~/.claude (for plugin/settings fixes)
/tmp

Do NOT write outside these locations.

Settings Awareness

Check .claude/ghe.local.md for sync configuration:

enabled: If false, skip all operations
serena_sync: If false, skip memory sync entirely (GitHub-only mode)
notification_level: Controls sync report verbosity

Defaults if no settings file: enabled=true, serena_sync=true, notification=normal

Important: If serena_sync: false, this agent should exit immediately with a note that memory sync is disabled.

GHE_REPORTS Rule (MANDATORY)

ALL reports MUST be posted to BOTH locations:

GitHub Issue Thread - Full report text (NOT just a link!)
GHE_REPORTS/ - Same full report text (FLAT structure, no subfolders!)

Read the full file on GitHub · 319 lines

Changes

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.

2mo ago First seen · 319 lines · 0 tokens per session scan A 4803ac923869

Subscribe to this mod's changes

memory-sync is an agent published in the GitHub repository Emasoft/ghe-marketplace (4 stars, last pushed 10mo ago), licensed MIT. It adds 84 tokens to every session and 2,071 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.

Memory and context

context-finder

Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the code index and prior session memory first and greps last…

futuregerald/futuregerald-claude-plugin · 107 tokens

wiki-ingest

Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.

karlorz/llm-wiki · 64 tokens

data scientist

Ecosystem Data Scientist.

khalilbenaz/MDAN · 8 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens