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/choria-io/fisk-ai/sessionsgit clone --depth 1 https://github.com/choria-io/fisk-aiWrote 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/agents/choria-io/fisk-ai/sessions)<a href="https://agentmods.dev/agents/choria-io/fisk-ai/sessions"><img src="https://agentmods.dev/badge/agents/choria-io/fisk-ai/sessions.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.00000 | $0.01830 |
| Opus 5 | $0.00000 | $0.00915 |
| Sonnet 5 | $0.00000 | $0.00366 |
| Haiku 4.5 | $0.00000 | $0.00183 |
Grade A, and why
sessions 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 5d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
+++ title = "Session snapshots" description = "journaling, continuing a conversation, and where sessions are stored" toc = true weight = 40 +++
Every run is a conversation, and every conversation is journaled. You do not turn this on. Leave a run and continue it later, in a fresh process or on another machine, using the id it prints when it ends.
Continuing a conversation
Ask something. fisk prints the id of the conversation when the run ends:
$ fisk run "report on the ORDERS stream"
Continue it by that id. No prompt is given, since the conversation is restored from the journal; passing one is an error:
$ fisk run --resume t-3f2a9c...
fisk reads the conversation back before it goes on, so you continue in context rather than from a blank screen.
Against an agent somewhere else, see remote agents, the journal is on the worker
rather than here, so --resume takes the conversation token instead of the id. fisk session show on the worker prints
it.
Chat sessions
Every full-screen run is a durable, resumable conversation.
Each turn is journaled, so the whole conversation survives leaving, a stop or a crash. Press Ctrl-D to leave the input
bar when you are finished for now; the status bar reads ctrl-d done. This does not end the conversation. fisk prints
how to continue it as it exits. Ctrl-C asks the current turn to stop at its next safe point. The conversation is kept
either way.
Resuming reads the conversation back into the viewport before the input bar opens, so you continue in context rather
than from a blank screen. Because the bar needs a real terminal, a conversation can only be continued in the full-screen
UI, not with --no-tui or over a pipe, where a run answers one prompt. A conversation has no "completed" state; remove
it with session rm once it is no longer needed.
Stopping
The first Ctrl-C, or a SIGTERM, asks the run to stop where the conversation can be continued: the current step
finishes, the turn is journaled, and fisk prints how to continue it. A second gives up on the run and leaves.
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.
- 5d ago First seen · 166 lines · 0 tokens per session scan A b71297b35e6a
sessions is an agent published in the GitHub repository choria-io/fisk-ai (5 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,830 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-31.
Other agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…
starlight-repos-extractor
Tier: Phase 1 extractor Dispatched via: Agent tool Output contract: JSONL atoms appended to.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.