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 skills/satsilem/ai-workflow-framework/end-sessionnpx skills add satsilem/ai-workflow-framework --skill end-sessiongit clone --depth 1 https://github.com/satsilem/ai-workflow-frameworkWrote 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/satsilem/ai-workflow-framework/end-session)<a href="https://agentmods.dev/skills/satsilem/ai-workflow-framework/end-session"><img src="https://agentmods.dev/badge/skills/satsilem/ai-workflow-framework/end-session.svg" alt="Measured on agentmods" 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 | $0.00085 | $0.02303 |
| Opus 5 | $0.00043 | $0.01151 |
| Sonnet 5 | $0.00017 | $0.00461 |
| Haiku 4.5 | $0.00009 | $0.00230 |
Grade A, and why
end-session 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 4d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
End Session
The goal is to close the session cleanly — capture what happened, update the project files, and surface anything worth remembering or acting on next time.
Two modes:
- Default — sequential: each section is presented one at a time, wait for confirmation before moving to the next.
- Quick mode — triggered when the user says "end session quick" or "quick end session": present all sections in one report, user replies once.
If mode is unclear, use default (sequential).
Step 1 — Read current state
Before producing the report, read:
SESSION.md— to understand what's already logged and what gotchas existTODO.md— to know the current task listCLAUDE.md— to check if anything critical needs updating.reference/INDEX.md— if present, to align on existing evergreen reference docs
Also review the full conversation history — this is the source of truth for what actually happened this session.
Step 2 — Produce the end-session report
Default mode (sequential)
Present each section one at a time. Wait for the user's reply before moving to the next. Order:
- Summary — show first, no confirmation needed, then immediately show Gotchas
- Gotchas to add to SESSION.md → wait for reply
- Tasks to mark as done → wait for reply
- Suggested new tasks → wait for reply
- INSIGHTS.md suggestions → wait for reply
- Apply all confirmed changes
Quick mode (all at once)
If the user said "end session quick" — present all sections in one block, user replies once for all sections. Same structure, same numbered lists.
In quick mode, start with a compact summary table before the detailed sections:
| Category | Count | Notes |
|---|---|---|
| Gotchas to add | N | include metadata tags |
| Tasks to mark done | N | include confidence tags |
| Suggested new tasks | N | deduped vs TODO.md |
| INSIGHTS suggestions | N | deduped vs INSIGHTS.md |
| Files to edit | N | SESSION.md / TODO.md / INSIGHTS.md |
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.
- 4d ago First seen · 276 lines · 85 tokens per session scan A 267bb9a1977a
end-session is a skill published in the GitHub repository satsilem/ai-workflow-framework (2 stars, last pushed 5mo ago), licensed MIT. It adds 85 tokens to every session and 2,303 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
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.
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.
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.
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…