mcpField
E
ecomode

ecomode

github.com/yeachan-heoAgent workflows33.7k100 installsUpdated today
Repository

About ecomode

Ecomode is a deprecated agent skill for routing work to lower-cost model tiers. It should not be invoked; the README directs users to `$ultrawork` for maintained high-throughput workflows.

Key features

  1. 01Deprecated; do not invoke
  2. 02Prefers lower model tiers
  3. 03Routes tasks by agent role
  4. 04Tracks lifecycle through omx state CLI

Use cases

  1. 01Not applicable for new workflows
  2. 02Refer to `$ultrawork` for high-throughput execution

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/yeachan-heo/oh-my-codex --skill ecomode

After installing, type/ecomodein Claude Code to confirm it loaded.

Bundled filesreferences/agent-tiers.md

Details

From the project README

Ecomode deprecated

Hard-deprecated. Do not invoke or route this skill. Use $ultrawork directly for maintained high-throughput execution workflows.

What Ecomode Does

Overrides default model selection to prefer cheaper tiers:

Default TierEcomode Override
THOROUGHSTANDARD, THOROUGH only if essential
STANDARDLOW first, STANDARD if needed
LOWLOW - no change

What Ecomode Does NOT Do

  • Persistence: Use ralph for "don't stop until done"
  • Parallel Execution: Use ultrawork for parallel agents
  • Delegation Enforcement: Always active via core orchestration

Combining Ecomode with Other Modes

Ecomode is a modifier that combines with execution modes:

CombinationEffect
eco ralphRalph loop with cheaper agents
eco ultraworkParallel execution with cheaper agents
eco autopilotFull autonomous with cost optimization

Ecomode Routing Rules

ALWAYS prefer lower tiers. Only escalate when task genuinely requires it.

DecisionRule
DEFAULTStart with LOW tier for most tasks
UPGRADEEscalate to STANDARD when LOW tier fails or task requires multi-file reasoning
AVOIDTHOROUGH tier - only for planning/critique if essential

Agent Selection in Ecomode

FIRST ACTION: Before delegating any work, read the agent reference file:

Read file: references/agent-tiers.md

This provides the complete agent tier matrix, MCP tool assignments, and selection guidance.

Ecomode preference order:

// PREFERRED - Use for most tasks
use /prompts:executor for this scoped task
use /prompts:explore for this scoped task
use /prompts:architect for this scoped task

// FALLBACK - Only if LOW fails
use /prompts:executor for this scoped task
use /prompts:architect for this scoped task

// AVOID - Only for planning/critique if essential
use /prompts:planner for this scoped task

Delegation Enforcement

Ecomode maintains all delegation rules from core protocol with cost-optimized routing:

ActionDelegate ToModel
Code changesexecutorLOW / STANDARD
AnalysisarchitectLOW
SearchexploreLOW
DocumentationwriterLOW
Background Execution

Long-running commands (install, build, test) run in background. Maximum 20 concurrent.

Token Savings Tips

  1. Batch similar tasks to one agent instead of spawning many
  2. Use explore (LOW tier) for file discovery, not architect
  3. Prefer LOW-tier executor routing for simple changes - only upgrade if it fails
  4. Use writer (LOW tier) for all documentation tasks
  5. Avoid THOROUGH-tier agents unless the task genuinely requires deep reasoning

Disabling Ecomode

Ecomode can be completely disabled via config. When disabled, all ecomode keywords are ignored.

Set in ~/.codex/.omx-config.json:

{
  "ecomode": {
    "enabled": false
  }
}

State Management

Use the CLI-first state surface (omx state ... --json) for ecomode lifecycle state. If explicit MCP compatibility tools are already available, equivalent omx_state calls are optional compatibility, not the default.

  • On activation: omx state write --input '{"mode":"ecomode","active":true}' --json
  • On deactivation/completion: omx state write --input '{"mode":"ecomode","active":false}' --json
  • On cancellation/cleanup: run $cancel (which should call omx state clear --input '{"mode":"ecomode"}' --json)

Comments

Markdown supported