A workflow for taking a coding task from intake and planning through execution, verification, repair, and acceptance. It is designed for one host agent and keeps records of the work and its evidence.

Use it when you need a repeatable, evidence-based process to plan changes, run checks, repair failures, and prove the result passes.

It organizes the steps needed to show that a change works, rather than stopping after the code has been written.

max — Skill by haoruilee

Install

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.

agentmods

npx agentmods add skills/haoruilee/oh-my-mcode/max

Any agent

npx skills add haoruilee/oh-my-mcode --skill max

Clone the repo

git clone --depth 1 https://github.com/haoruilee/oh-my-mcode

Made for: Claude Code, Codex.

Per session 123 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,267 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00123	$0.01267
Opus 5	$0.00062	$0.00633
Sonnet 5	$0.00025	$0.00253
Haiku 4.5	$0.00012	$0.00127

Measured 3d ago against content hash 12d9a7e26634, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

max 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 3d 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.

skills/max/SKILL.md · 64 lines

How it starts

The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Max Mode

Full verified-delivery loop on one host agent. Role files in agents/ are contracts this same agent must obey, not spawned personas. Never mark Accepted here. Hand acceptance to the verify skill.

中文名：验证交付模式。

Inputs

User goal, constraints, and any files they named.
Workspace root (project being changed). Plugin root is the installed copy, often ~/.minimax/plugins/oh-my-mcode.
State tool: node <plugin-root>/scripts/run-store.mjs (see references/run-store.md). Always write the same .minimax/runs layout. There is no second user-facing CLI to hand off to.
MCP first: if tools omm_run_create, omm_run_show, omm_run_list, omm_status, omm_verify, or omm_inspect exist, use them instead of hand-writing run files or inventing a second store. Do not set PLUGIN_ROOT / PLUGIN_DATA.

Procedure

INTAKE. Restate the goal in one sentence plus out-of-scope. Create the run: node <plugin-root>/scripts/run-store.mjs create --workspace <ws> --goal "<goal>" Persist run_id and the seeded acceptance list (goal-named command or detected test/build) before any host exec. Tell the user the path <ws>/.minimax/runs/<run_id>/ and how we will know we are done.
DISCOVER. CLI max may skip this host exec when the goal already names a file, function, or test command and the workspace has a detected test/build (--discover forces it). plan always discovers. When the explorer does run: set-phase --phase DISCOVER. Load agents/explorer.md. Read-only search and diagnostic commands only. Record risks and test entry points in notes, not in product files.
PLAN. set-phase --phase PLAN. Load agents/planner.md. Write plan.md and tasks.json via write-plan / write-tasks. Every task has one role and depends_on. Acceptance criteria must be commands or diffs a verifier can run without trusting the builder.
PLAN_REVIEW. set-phase --phase PLAN_REVIEW. Show the DAG and acceptance list. If the user asked for a plan only, stop and point them at the plan skill next time. If they asked to ship, continue unless they objected.
EXECUTE. set-phase --phase EXECUTE. Load agents/builder.md. Do one ready task. No scope creep. After the task: append-event --type task_completed --task-id T<n> and capture command output with add-evidence.
VERIFY. set-phase --phase VERIFY. Stop building. Follow skills/verify/SKILL.md and agents/verifier.md. The writer does not grade their own work.
REPAIR. If findings are rejected, a new Builder task is created from structured findings. Return to EXECUTE for that task only, then VERIFY again. Loop until Accepted or the user stops.
ACCEPT. Only the verify skill may leave status=accepted. After that, write evidence-report.
RELEASE. Only if the user asked to commit/PR and status is accepted. Load agents/release.md. Otherwise stop and present summary.md.

Read the full file on GitHub · 64 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/run-store.md 1.9 KB

Changes

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.

3d ago First seen · 64 lines · 123 tokens per session scan A 12d9a7e26634

Subscribe to this mod's changes

max is a skill published in the GitHub repository haoruilee/oh-my-mcode (51 stars, last pushed 4d ago), licensed MIT. It adds 123 tokens to every session and 1,267 once invoked, about $0.0006 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-30.

Planning

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens