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 skills add roedyrustam/vibes-plug --skill session-memory-managergit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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.
[](https://agentmods.dev/skills/roedyrustam/vibes-plug/session-memory-manager)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/session-memory-manager"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/session-memory-manager/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.
<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/session-memory-manager"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/session-memory-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00077 | $0.01728 |
| Opus 5 | $0.00039 | $0.00864 |
| Sonnet 5 | $0.00015 | $0.00346 |
| Haiku 4.5 | $0.00008 | $0.00173 |
Grade A, and why
session-memory-manager 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Memory Manager
English
Orchestration & Integration
Connects and orchestrates with relevant domain skills like brainstorming and zero-to-prod-orchestrator to ensure cohesive execution across the entire session lifecycle.
Description
This skill acts as the agent's memory controller. It handles loading project context at session startup, dynamically updating the context map and learning graph during the session, and seamlessly generating ultra-compact handoff checkpoints at session end.
1. Session Start (Ingestion)
Activate this phase IMMEDIATELY on a new session, or when the user says "start session" or "load context". Do not answer primary requests until complete.
Workflow:
- Discover Files: Search the root or
.docs/usinglist_dir,grep_search, orview_filefor:CONTEXT_MAP.md,LEARNING_GRAPH.md,PRD.md,BLUEPRINT.md(orARCHITECTURE.md), andCHECKPOINT.md. Also read tech stack identifiers (TECH_STACK.md,package.json,go.mod, etc.). - Internalize: Read the contents. Grasp the architectural constraints, user stylistic preferences, hard-learned lessons, and the current goal/milestone.
- Acknowledge: Briefly confirm to the user what context was loaded, stating the Tech Stack and immediate goal. Proceed to address the actual request.
2. Active Session (Run)
Maintain project memory actively to prevent context exhaustion and hallucination.
Maintain Context Map (CONTEXT_MAP.md)
- A highly compressed index (bullet points) of architecture, dependency graphs, and state locations.
- Rules: Do not store full code; use only file paths and 1-sentence responsibilities. Use BM25/
grep_searchbefore modifying. Append new major components/routes immediately upon creation.
Maintain Learning Graph (LEARNING_GRAPH.md)
- Triggers: When the user corrects code style, states a strong preference, or after resolving a complex bug.
- Rules: Physically write lessons to the memory file under categories: User Stylistic Preferences, Hard-Learned Lessons, Architectural Decisions. Do not just promise to remember.
- Global Memory: For issues spanning multiple projects, document the root cause/solution into a global context directory (e.g.,
<appDataDir>/knowledge). Inject this historical context proactively in future tasks.
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.
- today First seen · 129 lines · 77 tokens per session scan A b5c8722b738d
session-memory-manager is a skill published in the GitHub repository roedyrustam/vibes-plug (53 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,728 once invoked, about $0.0004 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-12.
Other skills, from other repositories
mm-setup
A setup guide that personalizes a shared mm system for one user. It asks for details such as your name, work area, tools, language, and Obsidian vault location, then saves them in private configuration files.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
session-management
Context preservation, tiered summarization, resumability.
context-shunt
Offload large / multi-file reads to a cheap worker model so raw files never enter Claude's context (token savings).
self-improve
Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past…
recall-reasoning
Recall the reasoning behind a past change by locating the Claude Code transcript that produced it. Use when the user asks to "recall reasoning", "find reasoning", "look up reasoning", "recall implementation reasoning", "find the rationale", "why did I do X", "recall from transcripts", or "find the transcript for this…