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 agents/sharrmavishal/operating-kit/session-endgit clone --depth 1 https://github.com/Sharrmavishal/operating-kitWhat 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.00000 | $0.00658 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
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 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.
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 thedeployagent 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
feedbackorprojectmemory? - 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/projectmemory (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
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 · 65 lines · 0 tokens per session scan A 8fd9e33cfbd1
session-end is an agent published in the GitHub repository Sharrmavishal/operating-kit (2 stars, last pushed 1mo 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.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
shep-web-route-creator
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…
python-pro
Python 3.13 language expert for the ClosedLoop plugin monorepo. Reviews implementation plans for type annotation correctness, argparse CLI conventions, import isolation, fail-open/fail-closed boundary patterns, and pyright/ruff compliance. Produces type-patterns.md in legacy mode.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…