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/Kenmege/codex-claude-companionWrote 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/kenmege/codex-claude-companion/doctor)<a href="https://agentmods.dev/commands/kenmege/codex-claude-companion/doctor"><img src="https://agentmods.dev/badge/commands/kenmege/codex-claude-companion/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/kenmege/codex-claude-companion/doctor"><img src="https://agentmods.dev/badge/commands/kenmege/codex-claude-companion/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.00020 | $0.00313 |
| Opus 5.5 | $0.00008 | $0.00125 |
| Sonnet 5.5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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
/claude-review:doctor
Preflight
- Prefer the helper binary
codex-claudeif it is available on PATH. - If it is not available, tell the user to install the helper with
npm install -g codex-claude-companionafter npmjs publish, or from a cloned checkout withnpm install -g ..
Plan
Runs the first-run diagnostic. It checks Node, Git, Claude Code CLI/version,
Claude auth, Codex plugin registration (including the native Codex plugin CLI
install path), writable job storage, non-Git folder support, and prompt
transport. Use --probe-runtime when the user wants live Claude
non-interactive model access checked as well.
Commands
Use the exact argument tail the user supplied after /claude-review:doctor.
- Preferred:
codex-claude doctor <user-arguments>
Useful flags:
--probe-runtime— run the live Claude model probe.--json— emit machine-parseable diagnostics.--config <path>— inspect a non-default Codex config path.--job-dir <path>— test a non-default job storage location.
Verification
If the helper exits non-zero, report the listed problem codes and recovery commands exactly.
Summary
Return the helper stdout verbatim.
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 · 44 lines · 20 tokens per session scan A e8561ff1ffdc
doctor is a command published in the GitHub repository Kenmege/codex-claude-companion (2 stars, last pushed 8d ago), licensed Apache-2.0. It adds 20 tokens to every session and 313 once invoked, about $0.0001 per session on Opus 5.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-08-31.
Other commands, from other repositories
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-explain
Trace execution step by step — use when code behavior is surprising or confusing.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
logic-locate
Locate the root cause of a confirmed failure — use when you have a stack trace, failing test, or wrong output.
logic-review
Review code for logic bugs — use when you suspect something is wrong but have no failing test yet.
db
Diagnose and fix a database bottleneck evidence-first — EXPLAIN, indexes, N+1, locks, pooling, safe migrations.