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 agentmods add skills/songshgeo/python-project-template/update-memory-banknpx skills add SongshGeo/Python-Project-Template --skill update-memory-bankgit clone --depth 1 https://github.com/SongshGeo/Python-Project-TemplateWhat 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.00064 | $0.00363 |
| Opus 5 | $0.00032 | $0.00181 |
| Sonnet 5 | $0.00013 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00036 |
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 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.
What it actually says
update-memory-bank
Keep memory-bank/ accurate. It is the persistent context both Cursor and Claude
Code read before working, so stale entries actively mislead.
What to update
architecture.md— when modules, boundaries, or key flows change. Keep it a concise map (prefer short descriptions + links to source-of-truth over long prose). Preserve thePurpose / Audience / Usageheader comment.model-design.md— when core entities, relationships, or invariants change. Favor small diagrams/examples over exhaustive detail.progress.md— append brief, actionable notes on what changed and the next steps; prune entries that are now resolved. This is a rolling worklog, not an archive.tech-stack.md— only when major dependencies or runtime/build tooling change.
How to work
- Diff intent vs. reality: read the relevant memory-bank file and the code it describes; note where they disagree.
- Make the smallest edit that restores accuracy. Do not invent structure that isn't in the code.
- Keep each file's existing header-comment convention intact.
- If a
memory-bank/plans/<task>.mdplan is now complete, summarize the outcome intoprogress.mdand remove or archive the plan.
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 · 33 lines · 64 tokens per session scan A ef0cb682c83d
update-memory-bank is a skill published in the GitHub repository SongshGeo/Python-Project-Template (8 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 363 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…