What is update-memory?

An agent instruction for creating or updating MEMORY.md, a repository file that records important past decisions and patterns for future coding sessions.

Use it to inspect the project and maintain a focused decision log for later AI sessions.

It helps coding agents avoid repeating rejected approaches or breaking architectural decisions.

update-memory — Agent for Claude Code by shuchitajain/awesome-ai-setup

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.

Clone the repo

git clone --depth 1 https://github.com/shuchitajain/awesome-ai-setup

Made for: Claude Code.

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/shuchitajain/awesome-ai-setup/update-memory/github.svg)](https://agentmods.dev/agents/shuchitajain/awesome-ai-setup/update-memory)

Your own site

<a href="https://agentmods.dev/agents/shuchitajain/awesome-ai-setup/update-memory"><img src="https://agentmods.dev/badge/agents/shuchitajain/awesome-ai-setup/update-memory/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/shuchitajain/awesome-ai-setup/update-memory"><img src="https://agentmods.dev/badge/agents/shuchitajain/awesome-ai-setup/update-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,863 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.00025	$0.01863
Opus 5.5	$0.00010	$0.00745
Sonnet 5.5	$0.00005	$0.00373
Haiku 4.5	$0.00003	$0.00186

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

Security

Grade A, and why

update-memory 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 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.

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.

agents/update-memory.md · 210 lines

How it starts

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

Update MEMORY.md

You are generating or updating a MEMORY.md file for this repository.

This file records decisions that should persist across AI sessions - architectural choices that were made (and should not be re-litigated), patterns that were abandoned (and should not be reintroduced), and anti-patterns specific to this codebase (that AI tools repeatedly get wrong).

MEMORY.md is a decision log, not documentation. It should be opinionated, direct, and focused on what AI tools need to know to avoid repeating past mistakes.

Step 1 - Read the Repository

Gather information to understand the current state and history.

Read these sources:

Dependency manifest (pubspec.yaml, package.json, etc.) - what's currently used tells you what was chosen. Look for what's notably absent (e.g., no flutter_bloc in a Flutter project means BLoC was either never used or was removed).
Primary source directory structure - the organizational pattern reveals architectural decisions.
State management files - how state is currently structured and what pattern is used.
Existing MEMORY.md or ARCHITECTURE.md if present - don't duplicate what's already there.
Comments and TODOs in code - // TODO: migrate this, // legacy: remove after X, // do not use Provider here - these are explicit memory signals left by developers.
Any CHANGELOG.md, DECISIONS.md, or ADR/ directory - formal decision records.
Test files - the mock strategy reveals decisions about test boundaries.

If git is available:

Run git log --oneline -50 to see recent commit history. Migration commits, refactor commits, and "remove X" commits are strong signals.
Check for commits with messages like "migrate from X to Y", "remove deprecated", "switch to", "replace".

Reference Example (Optional)

Check for a reference example in this order:

.ai/reference/*/MEMORY.md - if the user copied one during setup
node_modules/awesome-ai-setup/examples/*/MEMORY.md - if the package is installed locally

Read the full file on GitHub · 210 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.

1mo ago First seen · 210 lines · 25 tokens per session scan A 6743ec9f1c51

Subscribe to this mod's changes

update-memory is an agent published in the GitHub repository shuchitajain/awesome-ai-setup (5 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 1,863 once invoked, about $0.0001 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 ai ai-agents context-engineering github-copilot mcp

apm-expert

Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.

microsoft/apm · 39 tokens

gsd-mempalace-curator

Ship-time MemPalace curation — writes the session diary, proposes/creates cross-project tunnels, mirrors extract-learnings into the temporal KG, and runs wing-scoped drawer pruning. Spawned at ship:post by the mempalace capability.

open-gsd/gsd-core · 59 tokens

Plugin Tester

End-to-end plugin testing agent for OpenWebUI. Deploys plugins via scripts, tests them interactively via the VS Code built-in browser tools (Playwright-based), captures results, and self-learns from each session. Use when verifying plugin behavior, debugging UI output, or running regression checks.

Fu-Jie/openwebui-extensions · 63 tokens

Doc Writer

Handles all documentation for plugin changes in parallel with code implementation. Updates README, READMECN, docs mirrors, and standalone version files.

Fu-Jie/openwebui-extensions · 29 tokens

Plugin Implementer

Implement plugin code changes in parallel with Doc Writer. Follows the approved plan with strict project standards. No sequential handoffs.