Borrowing it
Nothing to install: this file belongs to rupakm/leslie. 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/rupakm/leslie/main/.claude/commands/ox-status.mdgit clone --depth 1 https://github.com/rupakm/leslieWrote 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/rupakm/leslie/ox-status)<a href="https://agentmods.dev/commands/rupakm/leslie/ox-status"><img src="https://agentmods.dev/badge/commands/rupakm/leslie/ox-status/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/rupakm/leslie/ox-status"><img src="https://agentmods.dev/badge/commands/rupakm/leslie/ox-status.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.00218 |
| Opus 5.5 | $0.00000 | $0.00087 |
| Sonnet 5.5 | $0.00000 | $0.00044 |
| Haiku 4.5 | $0.00000 | $0.00022 |
Grade A, and why
ox-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 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.
This is a copy
94% identical to status — 1 line 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 SageOx project status including authentication, sync, and daemon health.
Use when:
- Checking if you're logged in or authenticated
- Verifying project initialization and configuration
- Checking sync status of ledger and team context
- Confirming the daemon is running and healthy
- Getting an overview of SageOx state for this repository
Keywords: status, auth, sync, health, logged in, initialized, daemon, check, state, connected
Common Issues
Not logged in
Symptom: Status shows authentication as missing or expired
Solution: Run ox login to authenticate with SageOx cloud
Not initialized
Symptom: Status shows no SageOx configuration
Solution: Run ox init to initialize SageOx in this repository
Daemon not running
Symptom: Status shows daemon as offline or unreachable
Solution: Run ox daemon start to start the background sync daemon
$ox 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 · 28 lines · 0 tokens per session scan A 9a0e70fa57e4
ox-status is a command published in the GitHub repository rupakm/leslie (15 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 218 tokens. A static security scan graded it A with 0 findings. It is 94% identical to status, differing in 1 line, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.