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/ox/ox-statusgit 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-status)<a href="https://agentmods.dev/commands/sageox/ox/ox-status"><img src="https://agentmods.dev/badge/commands/sageox/ox/ox-status.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00225 |
| Opus 5 | $0.00000 | $0.00112 |
| Sonnet 5 | $0.00000 | $0.00045 |
| 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 4d 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
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.
- 4d ago First seen · 28 lines · 0 tokens per session scan A d545b5c5317e
ox-status is a command published in the GitHub repository sageox/ox (51 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 225 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
om-vault-upgrade
Import and migrate content from an existing Obsidian vault into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults.
om-vault-audit
Deep structural audit of the vault. Checks indexes, folder placement, frontmatter, links, Bases, and consistency. Fix what can be fixed, flag what needs user input.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
om-intake
Process all unread meeting notes in work/meetings/ — reads each file, classifies content, routes to the right vault notes, then clears the inbox.
om-wrap-up
Full session review before ending. Review context, ways of working, files modified, consistency, and suggest improvements.
om-peer-scan
Deep scan a peer's GitHub PRs for performance review preparation. Produces a structured analysis saved to perf/evidence/.