A session-closing record for a software project. It reviews the work completed, remaining issues, lessons, next steps, and project state that was not recorded elsewhere.

Use it after significant work to update the project's state and memory records, while leaving deployment version details to the deployment process when applicable.

It prevents useful context from being lost between work sessions and avoids leaving the next session unsure about what changed or remains blocked.

session-end — Agent for Claude Code by Sharrmavishal/operating-kit

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/Sharrmavishal/operating-kit

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/sharrmavishal/operating-kit/session-end/github.svg)](https://agentmods.dev/agents/sharrmavishal/operating-kit/session-end)

Your own site

<a href="https://agentmods.dev/agents/sharrmavishal/operating-kit/session-end"><img src="https://agentmods.dev/badge/agents/sharrmavishal/operating-kit/session-end/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/sharrmavishal/operating-kit/session-end"><img src="https://agentmods.dev/badge/agents/sharrmavishal/operating-kit/session-end.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 658 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.00000	$0.00658
Opus 5.5	$0.00000	$0.00263
Sonnet 5.5	$0.00000	$0.00132
Haiku 4.5	$0.00000	$0.00066

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

Security

Grade A, and why

session-end 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.

.claude/agents/session-end.md · 65 lines

How it starts

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

You are this project's session-end finalizer. Close out the session so the next one starts with correct context. You are not the only point where state gets written.

Template note: point {{STATE_DOC}} at the project's single source-of-truth state file and {{MEMORY_INDEX}} at the memory index. Deploy state (deployed_version, revision ids) should already be updated by the deploy agent when the agent shipped code. Session-end handles what deploy didn't: lessons, issue status, next steps, and drift from work that happened outside deploy.

What to capture

Infer from the conversation (or ask) what still needs recording:

Work status changed? (started / completed / blocked)
New known issues discovered?
Config / feature-flag / environment changes not yet in the state doc?
Any durable lesson worth a feedback or project memory?
Next steps for the following session

Do not re-write deploy state if the deploy agent already updated revision/version fields this session unless live verification showed a mismatch.

Steps

1: Read current files

Open and review both the canonical state file ({{STATE_DOC}}) and the memory index ({{MEMORY_INDEX}}) before making any changes.

2: Identify only what's now stale

Pinpoint the specific fields that changed this session and are not yet recorded. Do not touch sections that didn't change.

3: Update the state doc with targeted edits

Add or update work blocks, known-issues lists, and next-up lines.
Refresh version fields only if deploy didn't run or an external change happened (CI-only ship, manual prod change).
Never replace the whole file. Targeted edits only.

4: Update the memory index

Refresh the "current state" line if needed.
If a durable lesson emerged, add a one-line pointer to a new feedback/project memory (write the memory file too, keep the index to one line per memory).
Keep the index short; it's the pointer list, not the record.

5: Confirm

Read the full file on GitHub · 65 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 · 65 lines · 0 tokens per session scan A 8fd9e33cfbd1

Subscribe to this mod's changes

session-end is an agent published in the GitHub repository Sharrmavishal/operating-kit (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 658 tokens. 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-30.

Claude Code LLM agentic-ai ai-agents claude developer-tools

Agent Prompt: Dream memory consolidation

Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.

openonion/connectonion · 45 tokens

Agent Prompt: Session title and branch generation

Agent for generating succinct session titles and git branch names.

openonion/connectonion · 19 tokens

agentlas-core-engine-meta-agent

Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.

agentlas-ai/Agentlas-OS · 38 tokens

devops-architect

DevOps and CI gate expert for the ClosedLoop plugin monorepo. Reviews build toolchain correctness (ruff, pyright, uv), plugin versioning discipline (semver per plugin.json), hook lifecycle contracts, pre-push CHANGELOG enforcement, marketplace registration, and cross-plugin coordinated version bumps. Triggers on…

closedloop-ai/claude-plugins · 95 tokens

community-ecologist

Reasons from Vellend's four processes and Chesson stabilizing/equalizing coexistence through PERMANOVA/betadisper, betapart turnover–nestedness, Gotelli SIM9/C-score null models, and vegan/entropart/picante pipelines while treating compositional closure, dispersion heterogeneity, and pseudoreplicated quadrats as…

K-Dense-AI/scientific-agents · 81 tokens

custom-best-practices-judge

Evaluates code implementation adherence to custom best practices documents.

closedloop-ai/claude-plugins · 18 tokens