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/slowdoctor-dev/workspace-md/session-endnpx skills add slowdoctor-dev/workspace-md --skill session-endgit clone --depth 1 https://github.com/slowdoctor-dev/workspace-mdWrote 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/slowdoctor-dev/workspace-md/session-end)<a href="https://agentmods.dev/skills/slowdoctor-dev/workspace-md/session-end"><img src="https://agentmods.dev/badge/skills/slowdoctor-dev/workspace-md/session-end.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.00040 | $0.01185 |
| Opus 5 | $0.00020 | $0.00593 |
| Sonnet 5 | $0.00008 | $0.00237 |
| Haiku 4.5 | $0.00004 | $0.00119 |
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 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
session-end
When to use
Before disconnecting (end of work block, switching workspaces, etc.). Every session ends with a journal entry — the episodic trace per R3.
Requires
Requires 3-control/foundation/SOUL.md,
3-control/foundation/PRINCIPLE.md, and 2-mind/garden/essential/
to exist. If any are missing, run init instead of continuing.
Quick reference
| Step | Reads | Writes |
|---|---|---|
| 1. Summarize | git diff/log + session transcript | — |
| 2. Suggest commits | (per workspace convention) | Owner-accepted commits |
| 3. Write journal entry | session transcript, decisions | garden/essential/journal/<YYYY-MM-DD>-<runtime>-<NNN>.md |
| 4. Write fresh NEXT.md | outstanding work + open items | garden/essential/NEXT.md |
5. Chain to dream (optional) |
(handoff) | — |
Procedure
1. Summarize what changed
git diff --stat
git log --since="<session-start-time>" --oneline
git status --short
Show the Owner a digest: "This session added X, modified Y, did Z."
2. Suggest commits
For each meaningful uncommitted work unit, propose a commit message
in the workspace's convention (YYYY-MM-DD <short English summary>
default). Wait for Owner confirm before committing.
3. Write journal entry
Path: 2-mind/garden/essential/journal/<YYYY-MM-DD>-<runtime>-<NNN>.md
YYYY-MM-DD= today<runtime>= canonical runtime slug (see registry below)<NNN>= zero-padded ordinal within day+runtime (001,002, …; check existing entries to determine)
Fill the structure from garden/essential/journal/ENTRY-TEMPLATE.md.
Two sections need cross-action: Open / NEXT items also transfer to
fresh NEXT.md (step 4); Consolidations applied stays empty until
dream runs (step 5).
Runtime slug registry
Use one of these canonical filename slugs:
| Slug | Runtime |
|---|---|
claude |
Claude Code |
codex |
Codex CLI |
gemini |
Gemini CLI |
antigravity |
Antigravity |
cron |
headless scheduled run |
other |
any runtime not yet registered |
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 · 132 lines · 40 tokens per session scan A 5bae3a56bac0
session-end is a skill published in the GitHub repository slowdoctor-dev/workspace-md (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 1,185 once invoked, about $0.0002 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
memclaw
The agent's persistent long-term memory — the only knowledge that survives across sessions, shared across the fleet under access control. Consult it at the start of a task to recall prior decisions, findings, and rules before acting, and write outcomes, decisions, and lessons as work completes. Use whenever a caura…
company-brain
How an agent should operate as one mind inside a shared Company Brain built on Caura — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task compounds across the whole organization. Use this whenever you work as part of a Caura-connected team or fleet and your work…
marm-init
Guided MARM MCP setup. Invoke after running marm-memory init on the CLI to configure MARM memory across your agent. Drives transport choice, runtime choice, MCP config writing, multi-agent linking, and server start. Works on Claude, Codex, Gemini, Qwen, Cursor, VS Code, and other MCP-capable agents.
codex-memory-trim
Manage Codex's native global memory (/.codex/memories) with three sub-procedures - trim (audit + dedupe + three-layer cleanup), compress (rewrite verbose memories into concise form), and add-global (add a custom global rule/preference). Use when the user asks to 精简/清理/整理/压缩 Codex 记忆, 去重, 简化冗长记忆, 添加/写入/修改全局记忆 or a…
knowledge-repo-init
Guided wizard for connecting or scaffolding an optional knowledge / documentation repo to a Bridge instance. Walks the user through layout choice, area picks, frontmatter conventions, optional dual-doku contracts, Bridge wiring (ecosystem.yaml + workflow/contexts/), and copies template skeletons from…
compass-integrity
Use when the user is about to rely on prior session memory for a non-trivial decision, or when something feels off about a recall hit — runs the Merkle chain check, drift summary, and daemon liveness in one pass and surfaces any tampering, drift bursts, or daemon-down state before the user acts on stale or corrupted…