agentmods.dev

session-memory

A small session memory system that records important decisions and lessons so later work can continue with the same context.

In plain words
What is it for?
Use it to load prior project context at the start of work, consult it before important decisions, and save brief new lessons at the end.
Why use it?
It prevents repeated discoveries and inconsistent decisions across sessions or workflow steps.

Skill for Claude CodeCodex

5 4mo ago B scan 17 tokens original MIT
View the source file romiluz13/cc-teams
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/romiluz13/cc-teams/session-memory
Any agent
npx skills add romiluz13/cc-teams --skill session-memory
Clone the repo
git clone --depth 1 https://github.com/romiluz13/cc-teams

Made for: Claude Code, Codex.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,653 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.07653
Opus 5 $0.00009 $0.03827
Sonnet 5 $0.00003 $0.01531
Haiku 4.5 $0.00002 $0.00765

Measured 2d ago against content hash 0a6129882c05, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

session-memory scanned grade B with 1 finding 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 2d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

mkdir -p .claude/cc-teams && cat .claude/cc-teams/activeContext.md
plugins/cc-teams/skills/session-memory/SKILL.md · 772 lines

How it starts

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

Session Memory (MANDATORY)

The Iron Law

EVERY WORKFLOW MUST:
1. LOAD memory at START (and before key decisions)
2. PERSIST learnings at END (direct edit by memory owner, or Memory Notes handoff to memory owner)

Brevity Rule: Memory is an index, not a document. Be brief—one line per item.

Agent Teams Ownership Override (CC-Teams Default)

In CC-Teams team workflows, memory persistence is lead-owned by default:

  • Teammates: read memory + emit ### Memory Notes (For Workflow-Final Persistence).
  • Lead: executes the CC-TEAMS Memory Update task and writes .claude/cc-teams/*.
  • Only edit memory from a teammate if the prompt explicitly includes MEMORY_OWNER: teammate.

What "Memory" Actually Is (The Guts)

CC-Teams memory is a small, stable, permission-free Markdown database used for:

  • Continuity: survive compaction/session resets
  • Consistency: avoid contradicting prior decisions
  • Compounding: promote learnings into reusable patterns
  • Resumability: recover where a workflow stopped

CC-Teams also maintains lead-owned workflow artifacts for machine-readable execution state. Markdown memory is the human index. Workflow artifacts are the durable runtime truth.

Memory Surfaces (Types)

  1. Index / Working Memory: .claude/cc-teams/activeContext.md
    • "What matters right now": focus, next steps, active decisions, learnings
    • Links to durable artifacts (plans/research)
  2. Long-Term Project Memory: .claude/cc-teams/patterns.md
    • Conventions, architecture decisions, common gotchas, reusable solutions
  3. Progress + Evidence Memory: .claude/cc-teams/progress.md
    • What's done/remaining + verification evidence (commands + exit codes)
  4. Artifact Memory (Durable): docs/plans/*, docs/research/*
    • The details. Memory files are the index.
  5. Workflow Artifacts (Durable Runtime State): .claude/cc-teams/workflows/{workflow_instance}.json and .events.jsonl
    • Lead-owned machine-readable workflow state
    • Stores workflow identity, plan file, verification rigor, phase cursor, task ids, results, and captured memory notes
    • Resume prefers task metadata first, then workflow artifact, then Markdown memory
  6. Tasks (Execution State): Claude Code Tasks
    • Great for orchestration, but not guaranteed to be the only durable source.
    • Mirror key task subjects/status into progress.md for backup/resume.

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

  1. 2d ago First seen · 772 lines · 17 tokens per session scan B 0a6129882c05

Subscribe to this mod's changes

session-memory is a skill published in the GitHub repository romiluz13/cc-teams (5 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 7,653 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Memory and context
Related

Other skills, from other repositories

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