From agent-orchestration
Print the canonical agent → tier mapping (haiku / sonnet / opus) used across the laran/claude-methodology plugin family. Use to verify the active mapping, look up the tier for a specific agent, or remind yourself which agents bucket to which cost tier before dispatching.
npx claudepluginhub laran/claude-agent-orchestrationThis skill uses the workspace's default tool permissions.
Surfaces the active `subagent_type → tier` mapping.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Surfaces the active subagent_type → tier mapping.
/agent-roster # full table
/agent-roster <agent_name> # tier for one agent
/agent-roster --format json # JSON dump
Calls bin/agent-roster.sh, which resolves the mapping per this lookup
chain:
$AGENT_TIERS_FILE env var${CLAUDE_PROJECT_DIR}/.claude/agent-tiers.yml${HOME}/.claude/agent-tiers.ymlagent-orchestration/config/tiers.yml (canonical default)The output prints the source file path so you can confirm which file is active.
Claude Code's claude_code.token.usage metric carries the exact
model (e.g. claude-sonnet-4-6). For cross-model trend analysis and
budget reasoning, rolling N model identifiers up to 3 cost buckets
makes dashboards readable. The mapping is editorial — you decide which
agents belong in which bucket based on the role you cast them in,
not just the model they happen to be configured for.
Three options, depending on how broad the change should be:
.claude/agent-tiers.yml in the project root.~/.claude/agent-tiers.yml.agent-orchestration's
config/tiers.yml.File shape:
tiers:
my-custom-agent: opus
another-one: haiku
default: sonnet