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 haoruilee/oh-my-mcode --skill doctorgit clone --depth 1 https://github.com/haoruilee/oh-my-mcodeWrote 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/haoruilee/oh-my-mcode/doctor)<a href="https://agentmods.dev/skills/haoruilee/oh-my-mcode/doctor"><img src="https://agentmods.dev/badge/skills/haoruilee/oh-my-mcode/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/haoruilee/oh-my-mcode/doctor"><img src="https://agentmods.dev/badge/skills/haoruilee/oh-my-mcode/doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 37 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00088 | $0.00815 |
| Opus 5.5 | $0.00035 | $0.00326 |
| Sonnet 5.5 | $0.00018 | $0.00163 |
| Haiku 4.5 | $0.00009 | $0.00081 |
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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doctor
Honest install and package checks. No telemetry. No network.
中文名：插件自检。
Inputs
- Plugin root (repo checkout or
~/.minimax/plugins/oh-my-mcode). - Optional workspace, to test run-store writability.
Procedure
- Run the package checker (this is the real test):
node <plugin-root>/scripts/doctor.mjsDoctor requiresmcp.json, a non-emptymcpServerslist, andmcp/server.mjs. If MCP toolsomm_*exist, prefer them over hand-writing run files. - Suggest host commands that exist on mcode 0.1.6:
mcode --versionmcode plugin list --jsonmcode plugin list -m localmcode plugin list -m local --json
- Check the drop-in path
~/.minimax/plugins/oh-my-mcode. If the folder is missing, point atscripts/install.shorscripts/install.ps1. Do not send the user to MiniMax-AI/skills. - Confirm both manifests exist and list every packaged skill path (max, plan, verify, resume, doctor, review, ship, research, team, interview). Missing listed skills are an error, not a silent drop. Optional host smoke:
oh-my-mcode doctor --smoke(tinymcode execpong). Optional host TPS:oh-my-mcode doctor --tps— real stream-json usage, orunmeasuredif the host is missing/stubbed or omitsmessage.usage(non-zero unless--allow-stub). Do not invent tok/s. - Confirm
<workspace>/.minimax/runs/is creatable byrun-store.mjs createif the user wants a write probe.
Output contract
- Pass / fail from
doctor.mjs. - What was actually observed (
plugin listJSON if the command ran). - What cannot be proven: MiniMax Code has no public "is this Skill indexed?" inspect API. If the plugin is installed+enabled in
plugin listandSKILL.mdfiles exist, say so. Do not claim the model will definitely triggermax.
Failure handling
mcodenot on PATH: say so. Check the folder layout anyway.- Plugin present but disabled: tell the user to enable it in the marketplace UI; this repo does not invent a
plugin addrequirement for local drop-in (0.1.6 auto-enables copies under~/.minimax/plugins). displayNamefrom.minimax-plugin/plugin.jsonmay be ignored; the local catalog may show portableplugin.jsonname(oh-my-mcode). Report whichever string the host printed.
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 · 60 lines · 88 tokens per session scan A 0493a830aa6c
doctor is a skill published in the GitHub repository haoruilee/oh-my-mcode (51 stars, last pushed 2mo ago), licensed MIT. It adds 88 tokens to every session and 815 once invoked, about $0.0004 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-30.
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.
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…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.