agentsclimarketplace

Model policy

Skill leszekgruchala/buddy/skills/model-policy

Resolve Buddy stage tiers to exact Codex, Cursor, or Claude Code subagent models. Read before dispatching agents to apply project/user profiles, packaged defaults, native reasoning fields, fallbacks, and live validation.From its SKILL.md

Install
npx -y skills add leszekgruchala/buddy --skill model-policy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.6 KB, as published. Nobody here has run it

Model Selection Policy

This reference selects no stage or transition. Resolve one tier, then return control to the active skill. Do not activate another Buddy skill.

This is the runtime source of truth for stage tiers, packaged defaults, profile resolution, and dispatch. Stored preferences belong in .buddy/model-profile.yaml or ~/.buddy/model-profile.yaml, never this installed skill.

Stages and tiers

  • fast — bounded fact collection, normal implementation after a detailed spec, mechanical edits, narrow scope, low-risk changes, parallel fan-out over small files.
  • balanced — codebase analysis, solution-oriented research, direct implementation without a detailed spec, integration-heavy implementation, debugging, or phases whose brief names moderate ambiguity.
  • frontier — architecture, ambiguous design, cross-cutting refactors, decision settling inside spec, ideation.
StageDefaultRunner
researchbalanced; fast for bounded factsresearcher
innovatefrontierinnovator
specfrontierdeveloper main agent
specified implementfast by default per phaseone implementor per phase
direct implementbalanced by default per taskhost or bounded implementor

The developer orchestrator sequences stages and pins workers to their tier. Its own model remains the user's choice. Implementation uses per-phase implementors unless a phase says Main.

Packaged defaults

Use only when neither profile has the current product section:

cursor:
  fast:     composer-2.5-fast
  balanced: cursor-grok-4.6-high-fast
  frontier: kimi-k3-max
claude_code:
  fast:
    model: claude-sonnet-5
    effort: low
  balanced:
    model: claude-sonnet-5
    effort: high
  frontier:
    model: claude-opus-5
    effort: high
codex:
  fast:
    model: gpt-5.6-terra
    model_reasoning_effort: low
  balanced:
    model: gpt-5.6-terra
    model_reasoning_effort: high
  frontier:
    model: gpt-5.6-sol
    model_reasoning_effort: high
# opencode / unknown: omit model; inherit parent default.

Resolution

Before dispatch, check both profile paths. If either exists, first read the complete profile contract.

For the selected tier, choose:

  1. An explicit model override in the current task.
  2. Project profile's current-product section.
  3. User profile's current-product section, only if the project profile lacks it.
  4. Packaged current-product default, only if both profiles lack it.
  5. Orchestrator default when the selected value is inherit, invalid, incomplete, unsupported, or rejected by live dispatch.

A current-product section atomically replaces lower-priority mappings. File existence alone does not win: a project file lacking that section falls through to the user file. Never fill a missing, invalid, or rejected tier from a lower source. Preserve exact native strings and field names.

Resolution never edits profiles. Report a malformed or stale selected section, recommend configure-models, and omit its override.

When using packaged defaults, report once per top-level workflow: Using Buddy's packaged model defaults because no project or user profile configures this harness. Run configure-models to personalize them. Continue without repeating it per worker.

Reasoning controls

Codex stores model_reasoning_effort; dispatch it with model only through the live interface's exact field (for example reasoning_effort), never an unsupported config key. For every product, pass reasoning/effort only when that exact model and live interface support it; otherwise omit it.

Dispatch

  1. Resolve stage tier, then the explicit/profile/packaged definition.
  2. Before every override, revalidate the exact model against the live dispatch allowed list; shell catalogs prove discovery, not dispatch. For Cursor, follow cursor-task-dispatch.md.
  3. Send model only if its exact string is accepted. Send its exact reasoning/effort field and value only if supported for that model; otherwise omit the whole override.
  4. Never translate, normalize, abbreviate, guess, substitute, or borrow a model slug across products.
  5. If a saved definition is rejected, inherit and report that it needs reconfiguration; do not choose another concrete model.
  6. Omitting the override makes the worker inherit the orchestrator default, the required fallback for unsupported or unknown interfaces.

Keep looking

Skills are one crate of 610,220. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.