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-doctorgit 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-doctor)<a href="https://agentmods.dev/skills/sageox/ox/ox-cli-doctor"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-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/skills/sageox/ox/ox-cli-doctor"><img src="https://agentmods.dev/badge/skills/sageox/ox/ox-cli-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.00015 | $0.00291 |
| Opus 5 | $0.00008 | $0.00146 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
ox-cli-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 yesterday.
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:
- 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.
- yesterday First seen · 38 lines · 15 tokens per session scan A f5b6b2daab24
ox-cli-doctor is a skill published in the GitHub repository sageox/ox (51 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 291 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
health
Code Quality Dashboard. Runs the project's type-checker, linter, test runner, and dead-code detector, scores each category 0-10, and presents a dashboard with trends. Use when asked for a "health check", "code quality report", or "quality dashboard".
binary-analysis-patterns
Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.
Burp Suite Web Application Testing
This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core…
application-performance-performance-optimization
Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.
cpp-pro
Write idiomatic C++ code with modern features, RAII, smart pointers, and STL algorithms. Handles templates, move semantics, and performance optimization. Use PROACTIVELY for C++ refactoring, memory safety, or complex C++ patterns.
codebase-cleanup-refactor-clean
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.