Borrowing it
Nothing to install: this file belongs to sageox/ox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sageox/ox/main/.claude/commands/ox-session-abort.mdgit 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/ox-session-abort)<a href="https://agentmods.dev/commands/sageox/ox/ox-session-abort"><img src="https://agentmods.dev/badge/commands/sageox/ox/ox-session-abort/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/ox-session-abort"><img src="https://agentmods.dev/badge/commands/sageox/ox/ox-session-abort.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.00167 |
| Opus 5.5 | $0.00000 | $0.00067 |
| Sonnet 5.5 | $0.00000 | $0.00033 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade C, and why
ox-session-abort scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Keep this file thin. Behavioral guidance (use-when, post-command, errors) belongs in the ox CLI JSON output (guidance field), not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). --> Copies of this mod
1 near-identical copy found in the catalogue:
- ox-session-abort — 91% identical, 1 lines differ
What it actually says
Abort a session, discarding all local data without uploading to the ledger.
This is destructive and cannot be undone. Use /ox-session-stop to save instead.
To abort the current session: $ox agent session abort --force
To abort a specific session by name (useful for orphaned or stale sessions): $ox agent session abort --force
The session name can be the full name or a partial suffix (e.g., the agent ID like "OxKMZN").
Run ox session list to see session names and their status.
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 · 15 lines · 0 tokens per session scan C 96e5d2f69d5b
ox-session-abort is a command published in the GitHub repository sageox/ox (65 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 167 tokens. A static security scan graded it C with 1 finding (hidden instructions). 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.
0-setup
Scaffolds the project and sets up the Kamma environment.
1-plan
Plans a thread and generates thread-specific spec documents.
4-finalize
Finalizes a reviewed thread, updates project documentation, and handles cleanup.
loop
Plans a standing loop thread for repeated cycles of work.