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.
git 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/doctor)<a href="https://agentmods.dev/commands/sageox/ox/doctor"><img src="https://agentmods.dev/badge/commands/sageox/ox/doctor/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/doctor"><img src="https://agentmods.dev/badge/commands/sageox/ox/doctor.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.00184 |
| Opus 5.5 | $0.00000 | $0.00074 |
| Sonnet 5.5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
doctor 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.
What it actually says
Run diagnostic checks on SageOx configuration and integrations.
Use when:
- Something isn't working and you need to troubleshoot
- Verifying SageOx setup is correct after initialization
- Checking for configuration drift or broken integrations
- Debugging sync, auth, or daemon issues
- After upgrading ox CLI to verify compatibility
Keywords: doctor, diagnose, troubleshoot, fix, check, debug, health, verify, broken, issue
Common Issues
Setup required
Symptom: Doctor reports missing initialization
Solution: Run ox init to initialize SageOx in this repository
Checks failed
Symptom: One or more diagnostic checks report failures Solution: Follow the remediation steps doctor provides for each failed check
Daemon not running
Symptom: Doctor reports daemon is unreachable
Solution: Run ox daemon start to start the background sync daemon
$ox doctor
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 · 27 lines · 0 tokens per session scan A f4fc7ddade4a
doctor 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 184 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
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.