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-stop)<a href="https://agentmods.dev/commands/sageox/ox/session-stop"><img src="https://agentmods.dev/badge/commands/sageox/ox/session-stop/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-stop"><img src="https://agentmods.dev/badge/commands/sageox/ox/session-stop.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.00410 |
| Opus 5.5 | $0.00000 | $0.00164 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
session-stop 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
Stop recording and save this agent session to the project ledger.
Use when:
- Finishing a coding session and want to save the recording
- Wrapping up a feature, investigation, or bug fix
- Ending work for the day and want context preserved
- Before switching to a different task or repository
Keywords: session stop, save, finish, end, done, wrap up, stop recording, upload, ledger
Common Issues
Not recording
Symptom: no active session or similar error
Solution: No session is currently active. Run ox agent <id> session start first
LFS upload failed
Symptom: Session saved locally but upload to ledger failed Solution: Check network connectivity and retry. The session data is saved locally and can be pushed later
Summary generation slow
Symptom: Command hangs during "Generating summary..." Solution: Summarization runs client-side. Wait for completion or check network if it stalls
Post-Command: Generate and Push Summary (REQUIRED)
After the command completes, check the JSON output for a summary_prompt field.
This step is critical for session completeness - without it, the session has no rich summary.
If summary_prompt is present:
- Read the prompt carefully - it references the raw session file on disk
- Read the raw session file at the path specified in the prompt
- Generate the summary JSON following the Output Format in the prompt
- Save it to the exact path specified (typically
summary.jsonin the session cache dir) - If the prompt includes a
push-summarystep, run that command immediately - Verify the push succeeded by checking the JSON output for
"success": true
If summary generation fails:
- Run
ox agent <id> doctor- it can detect and help recover missing summaries - The session data is safe regardless; only the rich summary is missing
$ox agent session stop
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 · 43 lines · 0 tokens per session scan A 15f2cb1825ec
session-stop 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 410 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
brainstorm
A retired command for generating ideas before implementation. Its description says to use the Superpowers brainstorming skill instead.
setup-mcp-claude-code
Build and register the Contorium MCP server for Claude Code or Cursor Agent.
sages
Summon the Market Sages council to analyze a stock (e.g. /sages AAPL, /sages NVDA --value).
1-plan
Plans a thread and generates thread-specific spec documents.
0-setup
Scaffolds the project and sets up the Kamma environment.
4-finalize
Finalizes a reviewed thread, updates project documentation, and handles cleanup.