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.
git clone --depth 1 https://github.com/sageox/oxWrote 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/commands/sageox/ox/session-list)<a href="https://agentmods.dev/commands/sageox/ox/session-list"><img src="https://agentmods.dev/badge/commands/sageox/ox/session-list/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sageox/ox/session-list"><img src="https://agentmods.dev/badge/commands/sageox/ox/session-list.svg" alt="Reviewed on agentmods" width="80" 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.00156 |
| Opus 5.5 | $0.00000 | $0.00062 |
| Sonnet 5.5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
session-list 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 1mo 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.
What it actually says
List recent sessions from the project ledger and offer to view one.
Use when:
- Reviewing what happened in recent sessions
- Viewing a teammate's session
- Checking session history for context
Keywords: session list, sessions, history, recent, view, ledger
Steps
- Run the command below to show recent sessions:
$ARGUMENTS
If no arguments are provided, run:
ox session list --limit 5
- Present the results to the user and ask which session they'd like to view
- If the selected session's status column shows "stub", run
ox session download <name>first to fetch content from LFS - Run
ox session view <name>to open in the user's default format
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.
- 1mo ago First seen · 25 lines · 0 tokens per session scan A 2b1b1cde5b15
session-list is a command published in the GitHub repository sageox/ox (64 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 156 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 commands, from other repositories
kamma
Plans, implements, reviews, and finalizes a thread in a single run without requiring prior setup.
4-finalize
Finalizes a reviewed thread, updates project documentation, and handles cleanup.
gofer_hydrate
Reverse-engineer specification from existing code (Hydration).
gofer:check-workspace
Check whether this repo is initialized for Gofer and explain any missing or stale scaffold.
arckit.backlog
Generate prioritised product backlog from ArcKit artifacts - convert requirements to user stories, organise into sprints.
arckit.platform-design
Create platform strategy using Platform Design Toolkit (8 canvases for multi-sided ecosystems).