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 ProjAnvil/MindForge --skill session-summarygit clone --depth 1 https://github.com/ProjAnvil/MindForgeWrote 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/projanvil/mindforge/session-summary)<a href="https://agentmods.dev/skills/projanvil/mindforge/session-summary"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/session-summary/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/projanvil/mindforge/session-summary"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/session-summary.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.00058 | $0.00485 |
| Opus 5.5 | $0.00023 | $0.00194 |
| Sonnet 5.5 | $0.00012 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
session-summary 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 6d 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
Session Summary & Handover
You are an expert at context management and project continuity. Your goal is to capture the essence of the current development session so that work can continue seamlessly in a fresh environment.
When to Use
Trigger scenarios — use this skill when the user asks to:
- Summarize the current session for handover to a new session
- Document completed tasks and technical decisions
- Switch contexts without losing critical information
Your Responsibilities
- Analyze the current state: Review the recent interactions, file changes, and accomplished goals.
- Summarize Key Information:
- Goal: What was the main objective of this session?
- Progress: What exactly was achieved? (Files created, bugs fixed, features implemented)
- Context: Key technical decisions made, environment variables set, or specific constraints discovered.
- Open Issues: Any unresolved errors, blocked tasks, or partial implementations.
- Define Next Steps: A clear, prioritized list of what needs to be done immediately in the next session.
- Generate Handover Prompt: detailed prompt that the user can paste into the next session to restore context.
Handover Format
When asked to summarize the session, structure your response as follows:
1. Session Snapshot
- Objective: ...
- Status: [Completed / In-Progress / Blocked]
2. Accomplishments
- ...
- ...
3. Technical Context
- ...
4. Next Session To-Do
- Task 1
- Task 2
5. Restore Prompt (Copy & Paste this into new session)
[CONTEXT RESTORATION]
Project Path: <Current Path>
Last Session Summary:
<Insert Summary Here>
Immediate Tasks:
<Insert Next Steps Here>
Please review the current files and continue from where we left off.
What ships with it
1 file 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.
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.
- 6d ago Changed · +8 lines 99de96b98bc5
- 1mo ago First seen · 52 lines · 58 tokens per session scan A 0c0698aebe16
session-summary is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 485 once invoked, about $0.0002 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.
Other skills, from other repositories
memory
Use when sharpening a perception or observation you ALREADY formed about conversation state, user behavior, drift, emotional shifts, or cross-turn patterns. Trigger phrases include "what did you notice about X", "the user keeps doing Y", "I sense something has changed", "is the user X-ing", "what does this pattern…
wellread
Collective research memory for AI coding agents — search prior research before hitting the web, save findings back to the shared cache, view karma stats. Use when the user asks a library/API/framework question, before running WebSearch/WebFetch, or after deep web research so the next agent doesn't repay the cost.…
vp-context-save
Save current session state so any future session can resume without losing the thread. Captures: current hypothesis ID, last experiment ID, last skill run, what's pending, suggested next skill. Writes to /.vpstack/projects/{slug}/session-state.md. Run before ending a session, switching branches, or handing off to a…
vp-context-restore
Restore working context from a previous session. Reads session-state.md and presents a 2-sentence briefing: what you were doing and what to do next. Run at the start of any session after a break. Pair with /vp-context-save. (vpstack) Voice triggers: "restore context", "resume", "where was I", "pick up where I left…
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.