Route and operate OMK computer-use tasks across native desktop apps, WSL-to-Windows experiments, deterministic browser tools, Stagehand core, and Browserbase MCP without introducing a second orchestrator. Use when an OMK task must inspect or control macOS, Windows, Linux, Chrome, VS Code, Explorer, native GUI applications, browser sessions, screenshots, mouse/keyboard input, or structured web extraction.
Opt-in ultra-compressed OUTPUT style for OMK — port of JuliusBrussee/caveman (MIT, pin 0d95a81). Cuts output tokens ~65% (measured, range 22-87%) by speaking terse while keeping technical terms, code, errors, API names, CLI commands byte-exact. OUTPUT ONLY: 0% input/context/thinking reduction; adds ~1-1.5k input tokens per turn; net loss on terse Q&A or per-request/credit billing (Copilot etc). Six levels: lite / full (default) / ultra / wenyan-lite / wenyan-full / wenyan-ultra; switch via `/caveman <level>`. Trigger when user says "caveman", "/caveman", "talk like caveman", "brief mode", "less tokens", "be brief", "짧게 답해", "토큰 아껴", "간결하게". Opt-in ONLY (disable-model-invocation): never auto-fires; explicit invocation required. Code/commits/PRs stay normal style. Orthogonal to headroom (headroom = input/context compression; caveman = output prose).
Reverse-engineer and clone one or more websites in one shot — extracts assets, CSS, and content section-by-section and proactively dispatches parallel builder agents in worktrees as it goes. Use this whenever the user wants to clone, replicate, rebuild, reverse-engineer, or copy any website. Also triggers on phrases like "make a copy of this site", "rebuild this page", "pixel-perfect clone". Provide one or more target URLs as arguments.
Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", "ponytail-audit", or "/ponytail-audit". One-shot report, does not apply fixes.
Harvest every `ponytail:` comment in the codebase into a debt ledger, so the deliberate shortcuts and deferrals ponytail leaves behind get tracked instead of rotting into "later means never". Use when the user says "ponytail debt", "/ponytail-debt", "what did ponytail defer", "list the shortcuts", "ponytail ledger", or "what did we mark to do later". One-shot report, changes nothing.
Show ponytail's measured impact as a compact scoreboard: less code, less cost, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /ponytail-gain, "ponytail gain", "what does ponytail save", "show ponytail impact", "ponytail scoreboard".
Quick-reference card for all ponytail modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /ponytail-help, "ponytail help", "what ponytail commands", "how do I use ponytail".
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or invokes /ponytail-review. Complements correctness-focused review, this one only hunts complexity.