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 commands/sageox/agentx/ox-session-statusgit clone --depth 1 https://github.com/sageox/agentxWhat 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 | $0.00000 | $0.00235 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
ox-session-status 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 2d 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.
This is a copy
91% identical to ox-session-status — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Check the status of all active session recordings in this project.
Post-Command
After the command completes, check the JSON output:
recording: true— A session is active. Continue working normally.recording: false— No active session. Consider running/ox-session-startif you want to record.guidance— Follow any guidance returned by the CLI.entry_count— Number of entries captured so far.count > 1— Multiple concurrent recordings. Thesessionsarray shows each one.agent_id— The agent ID of the recording. Compare with your own to identify your session.
$ox session status --json --current
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.
- 2d ago First seen · 18 lines · 0 tokens per session scan A 418898956962
ox-session-status is a command published in the GitHub repository sageox/agentx (4 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 235 tokens. A static security scan graded it A with 0 findings. It is 91% identical to ox-session-status, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
iterate
Iteration delivery — delivery check + archive + commit & tag + bump version.
init
Initialize dev-flow project — scan current state, create/align .dev-doc, update agent instruction file.
task
Start TASK phase — task decomposition.
mode
Select development mode — control flow phases.
issue
DOCROOT obtained via dow status --field docroot.
fix
User-triggered workflow to automatically fix open issues.