fedorovvvv

Omp Agent Role Router — AI skill for Claude Code

AI community

omp extension: routes Claude Code / Codex plugin subagents to omp model roles by declared tier.

How to install Omp Agent Role Router

This entry records only its repository, not the path inside it, so there is no exact command to give. Open fedorovvvv/omp-agent-role-router and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Omp Agent Role Router does

omp extension: routes Claude Code / Codex plugin subagents to omp model roles by declared tier.

Alternatives in AI

Agency Orchestrator — 🚀 One sentence → multi-AI-role collaboration → complete plan in minutes 453 ★
Module Feature — Add a new feature (model + service + controller + views + routes + tests) to an existing module 407 ★
Herdr Agent Usage — Credential-scoped AI quota, context, and cache in Herdr for Claude, Codex, Grok, Agy, OpenCode, Pi, omp, Devin 131 ★

README

omp-agent-role-router

An [omp](https://github.com/can1357/oh-my-pi) extension that gives Claude Code plugin subagents back a sensible model.

The problem

omp drops the `model:` field of agents that come from Claude Code marketplace plugins (`opus`, `sonnet`, `haiku` in their frontmatter). Without that field, a subagent has no model of its own — it just runs on whatever model your main session happens to be on right now, including a mid-turn retry fallback. A `haiku`-tier agent can end up burning `opus`. A `sonnet`-tier reviewer can end up running on your session's accidental Codex fallback.

	without this extension	with this extension
`guardian` (`opus`)	whatever your session is on	`@default`
`planner` (`sonnet`)	whatever your session is on	`@task`
`forge-advisor` (`haiku`)	whatever your session is on	`@smol`

It reads each agent's own declared tier and gives it an omp **role** (`@default`, `@task`, `@smol`, …) instead — never a concrete model. What that role actually resolves to is still entirely up to your own `modelRoles`.

Install

omp plugin install github:fedorovvvv/omp-agent-role-router

No build step, nothing else to configure. It works immediately.

Default mapping

declared tier	routed to
`opus`	`@default`
`sonnet`	`@task`
`haiku`	`@smol`
`gpt-flagship` (Codex `sol`/`astra`/…)	`@default`
`gpt-mid` (Codex `terra`/`*-codex`)	`@task`
`gpt-mini` (Codex `luna`/`-mini`/`-nano`)	`@smol`

Configuration

Zero-config already does the right thing. To change it, add an `agentRoleRouter` block to `~/.omp/agent/config.yml` or `/.omp/config.yml`:

agentRoleRouter:
  tiers:
    opus: "@slow" # change what a whole tier routes to
  agents:
    guardian: "@slow" # override one specific agent by name
    noisy-agent: false # leave this one alone, whatever its tier
  plugins:
    some-plugin: false # leave every agent of this