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 usefulmove/enso --skill enso-session-persistgit clone --depth 1 https://github.com/usefulmove/ensoWrote 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/usefulmove/enso/enso-session-persist)<a href="https://agentmods.dev/skills/usefulmove/enso/enso-session-persist"><img src="https://agentmods.dev/badge/skills/usefulmove/enso/enso-session-persist.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.1 | $0.00021 | $0.00537 |
| Opus 5 | $0.00010 | $0.00269 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
enso-session-persist 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 7d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Contract
Persist session state across the ephemeral -> durable seam. Write the smallest useful durable update. Skip ceremony that will not help a future agent or human resume work.
Principles
- Persist deltas, not transcripts.
- Prefer active story progress, decisions, next steps, reusable lessons, and handoff notes.
- Do not create generic logs, lessons, or reflection prompts unless they have future value.
- Respect local harness shape.
docs/stories/,docs/logs/, anddocs/reference/LESSONS.mdare conventions, not requirements. - If write/edit tools are available,
/enso-persistcounts as permission to write the minimal checkpoint after a concise proposal. - If only read-only tools are available, generate the proposed diff/content and ask the user to apply or switch modes.
Minimal Probe
Use lightweight read-only inspection as needed:
git status --short 2>/dev/null || true
ls -t docs/stories/*.md 2>/dev/null | head -5 || true
ls -t docs/logs/*.md 2>/dev/null | head -3 || true
[ -f docs/reference/LESSONS.md ] && tail -80 docs/reference/LESSONS.md || true
Read only the files needed to decide what is worth persisting.
Persistence Proposal
Before writing, show a compact proposal:
Persist proposal:
- <file>: <why this durable update is useful>
Content:
- Decisions: <only new durable decisions>
- Progress: <only useful resume state>
- Next: <next concrete step>
- Lessons: <only reusable lessons, or "none">
Then proceed according to available tools:
- With write/edit tools: write the proposed minimal checkpoint.
- Read-only mode: provide a patch or exact content block and ask the user to apply it.
Write Targets
Choose the smallest appropriate target:
- Active story: progress, decisions, verification state, next step.
docs/logs/YYYY-MM-DD-session.md: session-level handoff when no active story is right, or when a log improves re-entry.docs/reference/LESSONS.md: only reusable lessons that should survive this task.- New skill/story/reference doc: only when the session exposed a repeated capability or durable concept worth naming.
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.
- 7d ago First seen · 69 lines · 21 tokens per session scan A d343de41edd9
enso-session-persist is a skill published in the GitHub repository usefulmove/enso (2 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 537 once invoked, about $0.0001 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
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…
capabilities
Your capability catalog — read this at boot. Lists the temporal date-range skills and the external integrations (reached via the loopback broker) available to you as a spawned worker, and exactly how to call each. Read-only. Consult it whenever you're unsure what tools/integrations you have or how to invoke them.
temporal
Resolve ANY named time window — today, yesterday, thisWeek, lastWeek, last7Days, last30Days, last90Days, thisMonth, lastMonth, thisQuarter, lastQuarter, thisYear, lastYear, last12Months — or an arbitrary range (lastNdays / lastNweeks / lastNmonths) to a concrete ISO date range relative to your run time. Read-only: no…
md-audit
Read-only code quality audit — scan the current working directory for common issues (bugs, dead code, security hotspots, missing error handling) and return a prioritised findings report. No files are edited. Use when asked to "audit the code", "quick audit", "find issues", "code scan", or "what's wrong with this…
last30Days
Resolve "last30Days" to a concrete ISO date range relative to your run time — a rolling 30-day window ending today. Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a "last 30 days" / trailing-month task…
thisQuarter
Resolve "thisQuarter" to a concrete ISO date range relative to your run time — this quarter so far (quarter start → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a quarter-to-date task (QTD…