update-memory-bank

update-memory-bank is a skill for Claude Code, Cursor from emaraschio/cursor-commands. It costs 10 tokens per session (461 once invoked), scanned A, original, MIT.

A procedure for updating a repository's memory bank: files that record current work, progress, technology choices, and established patterns.

In plain words
What is it for?
Use it after feature work, meaningful commits, technology changes, or when the recorded project context may be outdated.
Why use it?
It keeps the agent's project context aligned with the actual repository after significant changes or long work sessions.

Skill for Claude CodeCursor

Written for Claude Code and Cursor: user-invocable in frontmatter, but also installed under .cursor/.

Good fit Use it after feature work, meaningful commits, technology changes, or when the recorded project context may be outdated.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/emaraschio/cursor-commands/update-memory-bank
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.

Any agent
npx skills add emaraschio/cursor-commands --skill update-memory-bank
Clone the repo
git clone --depth 1 https://github.com/emaraschio/cursor-commands

Made for: Claude Code, Cursor.

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.

agentmods badge for update-memory-bank

README.md
[![agentmods](https://agentmods.dev/badge/skills/emaraschio/cursor-commands/update-memory-bank/github.svg)](https://agentmods.dev/skills/emaraschio/cursor-commands/update-memory-bank)
Your own site
<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/update-memory-bank"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/update-memory-bank/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.

agentmods 80×15 button for update-memory-bank

Your own site · 80×15
<a href="https://agentmods.dev/skills/emaraschio/cursor-commands/update-memory-bank"><img src="https://agentmods.dev/badge/skills/emaraschio/cursor-commands/update-memory-bank.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 461 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00461
Opus 5 $0.00005 $0.00230
Sonnet 5 $0.00002 $0.00092
Haiku 4.5 $0.00001 $0.00046

Measured 5d ago against content hash 089d2411d681, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

update-memory-bank 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 5d 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.

.cursor/skill-contracts/update-memory-bank/SKILL.md · 47 lines

What it actually says

Overview

Sync the memory bank with the current state of the repository and recent agent interactions. Run after significant work sessions, feature completions, or when context has drifted from reality.

Memory Bank Files

Each file has a distinct responsibility. Update only what changed:

File Purpose Update when...
activeContext.md Current state, recent commits, active work After any meaningful commits
progress.md Changelog, milestones, statistics After feature completion
techContext.md Tech stack, tools, environment Tech stack changes
systemPatterns.md Coding standards, patterns New patterns established
projectbrief.md Project purpose and scope Rarely, only on major scope shifts

Steps

  1. Gather current state

    • Run git log --oneline -15 to capture recent commits
    • Note any new files, commands, or rules added since last update
    • Check activeContext.md "Last Updated" date to understand the gap
  2. Update each relevant file

    • activeContext.md: Update "Last Updated" date, "Latest Commits" list, "Recent Focus Areas", and "Cursor Commands Inventory" count if it changed
    • progress.md: Add a changelog entry for the current month if work occurred; update statistics if counts changed
    • Other files: Only touch if their specific domain changed
  3. Verify accuracy

    • Confirm commit hashes and descriptions match git log output
    • Remove stale "Active Work Items" that are now complete
    • Ensure statistics (command count, etc.) reflect reality
  4. Commit

    • Use format: docs(memory-bank): update memory bank with latest changes
    • Stage only memory bank files: git add .cursor/memory-bank/
    • Push to remote after commit

Guardrails

  • Record only verified state; do not invent commits, files, or statistics.
  • Update only the files whose domain changed; leave unchanged files alone.
Files

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.

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.

  1. 5d ago First seen · 47 lines · 10 tokens per session scan A 089d2411d681

Subscribe to this mod's changes

update-memory-bank is a skill published in the GitHub repository emaraschio/cursor-commands (9 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 461 once invoked, about $0.0001 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-09-03.