Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Jerrylalala/compound-engineeringnpx agentmods add skills/jerrylalala/compound-engineering/ce-doctorWrote 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/jerrylalala/compound-engineering/ce-doctor)<a href="https://agentmods.dev/skills/jerrylalala/compound-engineering/ce-doctor"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/ce-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/jerrylalala/compound-engineering/ce-doctor"><img src="https://agentmods.dev/badge/skills/jerrylalala/compound-engineering/ce-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.00021 | $0.01050 |
| Opus 5 | $0.00010 | $0.00525 |
| Sonnet 5 | $0.00004 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade A, and why
ce: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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doctor 健康检查与自动配置
检测 CLI 工具(Codex/Gemini)、MCP 服务器(GitHub/Context7)、认证状态,支持 --fix 一键自动修复。
参数说明
- 无参数:仅检测并报告(快速模式)
--fix:自动安装缺失的必需项(Codex CLI、Gemini CLI、GitHub MCP)--smoke:额外执行冒烟测试验证 CLI 可用性--fix和--smoke可组合使用
执行步骤
Step 1: 运行健康检查
直接调用现有脚本(不依赖不存在的 doctor.sh):
版本一致性检查(始终执行):
powershell -ExecutionPolicy Bypass -File scripts/check-versions.ps1
CLI 工具检查(始终执行):
# 检查 Codex
command -v codex && codex --version 2>/dev/null || echo "FAIL: Codex 未安装"
# 检查 Gemini
command -v gemini && gemini --version 2>/dev/null || echo "FAIL: Gemini 未安装"
# 检查 GitHub CLI
gh --version 2>/dev/null || echo "FAIL: GitHub CLI 未安装"
MCP 服务器检查(始终执行):
# 检查 GitHub MCP
claude mcp list 2>/dev/null | grep -i github || echo "WARN: GitHub MCP 未配置"
# 检查 Context7 MCP
claude mcp list 2>/dev/null | grep -i context7 || echo "WARN: Context7 MCP 未配置"
Handoff 协议检查(始终执行):
bash scripts/check-handoff.sh
如果 $ARGUMENTS 包含 --smoke,额外执行:
# 冒烟测试:验证 Codex 可执行简单任务
echo "echo hello" | codex exec - 2>/dev/null && echo "PASS: Codex smoke test" || echo "FAIL: Codex smoke test"
如果 $ARGUMENTS 包含 --fix,对 FAIL 项给出修复命令(见 Step 3)。
Step 2: 格式化输出
将脚本输出格式化为 Markdown 表格展示给用户:
## 健康检查报告
| 状态 | 检查项 | 详情 |
|------|--------|------|
| PASS | Codex CLI | 已安装 (x.x.x) |
| PASS | Gemini CLI | 已安装 (x.x.x) |
| PASS | GitHub MCP | 已配置(全局) |
| PASS | Context7 MCP | 已在 plugin.json 中配置 |
| WARN | agent-browser | 未安装(可选) |
| ... | ... | ... |
**汇总**: PASS: X WARN: X FAIL: X FIXD: X
Step 3: 给出修复建议
针对 FAIL 和 WARN 项,给出具体修复命令:
- Codex 未安装 →
npm install -g @openai/codex - Gemini 未安装 → 参考 Google 官方安装文档
- 模型过旧 → 提示编辑配置文件更新模型
- 认证缺失 → 提示运行首次登录
- GitHub MCP 未配置 →
CLAUDECODE= claude mcp add --transport http github https://api.githubcopilot.com/mcp/ - agent-browser 未安装 →
npm install -g agent-browser(可选)
提示用户可使用 --fix 参数自动修复必需项。
Step 4: 自动修复后提醒
如果使用了 --fix 并成功修复了 MCP 配置(如 GitHub MCP),提醒用户:
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.
- 9d ago First seen · 110 lines · 21 tokens per session scan A bd971f8ef465
ce:doctor is a skill published in the GitHub repository Jerrylalala/compound-engineering (5 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 1,050 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-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.