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 skills add sageox/ox --skill ox-cli-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/skills/sageox/ox/ox-cli-status)<a href="https://agentmods.dev/skills/sageox/ox/ox-cli-status"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-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/skills/sageox/ox/ox-cli-status"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-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.00018 | $0.00300 |
| Opus 5 | $0.00009 | $0.00150 |
| Sonnet 5 | $0.00004 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
ox-cli-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 today.
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
Explicit invocation only. Run this when the user asks for it by name. It performs a lifecycle or diagnostic action with side effects, so never invoke it on your own initiative.
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.
- today First seen · 38 lines · 18 tokens per session scan A 9dc38e7d4ffb
ox-cli-status is a skill published in the GitHub repository sageox/ox (51 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 300 once invoked, about $0.0001 per session on Opus 5. 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-09-08.
Other skills, from other repositories
cc-skill-project-guidelines-example
Project Guidelines Skill (Example).
multica-goal-tracker
Track goal-driven Multica issues. Use when a user creates or maintains Multica issues by pasting a /goal prompt, wants Codex to summarize that goal into a concise issue purpose, append a normalized goal-start comment, record completion evidence from real Multica execution run messages or a supplied session transcript…
notification-report
A skill that collects unread notifications from subscribed workspaces into one report. Users can review the report and send replies back to the workspaces that produced the notifications.
teamwork-parent
A workflow for splitting a large issue into smaller sub-issues and coordinating their separate worktrees. A worktree is an isolated copy of a Git project where one task can be developed independently.
teamwork-child
A workflow rule for a worktree created for a child issue, which is a smaller task split from a larger issue. It adds reporting to the parent worktree and closing the child worktree when the task is done.
worktree-assign
A worktree assignment guide for creating a Git worktree and sending a coding task to an AI agent. A worktree is a separate working directory that lets a branch be worked on independently.