agentleFS
lza6lza6/claw-code-tingfeng/skills/ecomode/SKILL.md

ecomode

Skill5 starsChanged 12 days agoMITView on GitHub

Token-efficient model routing modifier

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Persistence: Use ralph for "don't stop until done"

    line 33
  2. Very specific:

    Parallel Execution: Use ultrawork for parallel agents

    line 34
  3. Distinctive:

    Delegation Enforcement: Always active via core orchestration

    line 35
  4. Distinctive:

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

    line 59
  5. Very specific:

    Use omx_state MCP tools for ecomode lifecycle state.

    line 118

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

clawd 路径适配(重要):本技能移植自 oh-my-codex,文中所有 ~/.codex/...、 .codex/skills/、CODEX_HOME 都是 Codex 时代的路径。在 clawd 里真实生效的是:

  • 技能位置:<项目>/skills/<name>/SKILL.md(支持分组子目录,如 skills/reverse/<sub>/SKILL.md,发现逻辑是递归的)
  • 运行期数据/配置:<项目>/.clawd/(sessions/、logs/、features.json 等)
  • 查当前实际发现到的技能:clawd hud 或直接调 skill 工具;诊断环境用 clawd doctor

只有当你确实在 Codex 里运行本技能时,~/.codex/... 那套路径才成立。 在 clawd 里照着 ~/.codex/... 找文件只会得到"不存在"。

Ecomode Skill

Token-efficient model routing. This is a MODIFIER, not a standalone execution mode.

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: docs/shared/agent-tiers.md

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

Ecomode preference order:

// PREFERRED - Use for most tasks
delegate(role="executor", tier="LOW", task="...")
delegate(role="explore", tier="LOW", task="...")
delegate(role="architect", tier="LOW", task="...")

// FALLBACK - Only if LOW fails
delegate(role="executor", tier="STANDARD", task="...")
delegate(role="architect", tier="STANDARD", task="...")

// AVOID - Only for planning/critique if essential
delegate(role="planner", tier="THOROUGH", 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 omx_state MCP tools for ecomode lifecycle state.

  • On activation: state_write({mode: "ecomode", active: true})
  • On deactivation/completion: state_write({mode: "ecomode", active: false})
  • On cancellation/cleanup: run $cancel (which should call state_clear(mode="ecomode"))

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.