A project-memory command that regenerates instruction files for several coding tools from one shared decision file.

For updating GitHub Copilot instructions, Cursor rules, and the project’s CLAUDE.md file, then reporting updated files, synced decisions, and cumulative statistics.

It keeps tool-specific instruction files aligned with the project’s recorded decisions.

memory-sync — Skill by sunil-goyal-1502

Install

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.

agentmods

npx agentmods add skills/sunil-goyal-1502/project-memory/memory-sync

Any agent

npx skills add sunil-goyal-1502/project-memory --skill memory-sync

Clone the repo

git clone --depth 1 https://github.com/sunil-goyal-1502/project-memory

Made for: Claude Code, Codex.

Or install project-memory, the plugin that ships this one along with the rest of its 11 skills, 2 agents, 1 MCP server.

Per session 8 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 0 findings. Scan, not verified.

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	$0.00008	$0.00308
Opus 5	$0.00004	$0.00154
Sonnet 5	$0.00002	$0.00062
Haiku 4.5	$0.00001	$0.00031

Measured 3d ago against content hash 77806e0d9649, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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.

skills/memory-sync/SKILL.md · 30 lines

What it actually says

Sync Project Decisions to Tool Files

Regenerate all tool-specific instruction files from the canonical decision store.

Steps

Verify .ai-memory/decisions.jsonl exists. If not, tell the user to run /project-memory:memory-init first.

Run the sync script:

node -e "require('${CLAUDE_PLUGIN_ROOT}/scripts/sync-tools.js').syncAll(process.cwd())"

This will regenerate:
- .github/copilot-instructions.md — Decisions grouped by category + self-referential save instructions for GitHub Copilot
- .cursor/rules/project-decisions.mdc — Decisions with frontmatter + save instructions for Cursor
- CLAUDE.md — Updated decisions section between  and  markers
Report results: Confirm which files were updated and how many decisions were synced.

Show cumulative stats: Read stats from .ai-memory/metadata.json and display cumulative savings line:

node -e "const s=require('${CLAUDE_PLUGIN_ROOT}/scripts/stats.js');const st=s.getStats(process.cwd());console.log(s.formatStatsLine(0,0,st))"

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.

3d ago First seen · 30 lines · 8 tokens per session scan A 77806e0d9649

Subscribe to this mod's changes

memory-sync is a skill published in the GitHub repository sunil-goyal-1502/project-memory (8 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 308 once invoked, about $0.0000 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.

Memory and context

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens