Mmcp.market

model-profile-resolution skill

by a5c-ai·a5c-ai/babysitter·1.8k stars·MIT

Resolve model profile (quality/balanced/budget) at orchestration start and map agents to specific models. Enables cost/quality tradeoffs by selecting appropriate AI models for each agent role.

A100/100content scan

Is the model-profile-resolution skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the model-profile-resolution skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/a5c-ai/babysitter.git /tmp/babysitter
mkdir -p ~/.claude/skills
cp -r /tmp/babysitter/library/methodologies/gsd/skills/model-profile-resolution ~/.claude/skills/model-profile-resolution
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

  • balanced: Mix of high and mid-tier models. Good quality at moderate cost. Default profile.
  • budget: Cheapest viable models for all agents. Acceptable quality at minimum cost.

The active profile is stored in .planning/config.json under the profile field, or can be overridden with the --profile flag.

Capabilities

1. Read Active Profile

Load the current profile from configuration:

// .planning/config.json
{
  "profile": "balanced",
  ...
}

If no profile is set, default to balanced.

2. Profile Definitions

Each profile maps agent roles to specific models:

quality:
  orchestrator: claude-opus-4-6
  gsd-planner: claude-opus-4-6
  gsd-executor: claude-opus-4-6
  gsd-verifier: claude-opus-4-6
  gsd-plan-checker: claude-opus-4-6
  gsd-phase-researcher: claude-opus-4-6
  gsd-project-researcher: claude-opus-4-6
  gsd-research-synthesizer: claude-opus-4-6
  gsd-roadmapper: claude-opus-4-6
  gsd-codebase-mapper: claude-opus-4-6
  gsd-debugger: claude-opus-4-6
  gsd-integration-checker: claude-opus-4-6

balanced:
  orchestrator: claude-opus-4-6
  gsd-planner: claude-sonnet-4
  gsd-executor: claude-sonnet-4
  gsd-verifier: claude-sonnet-4
  gsd-plan-checker: claude-sonnet-4
  gsd-phase-researcher: claude-sonnet-4
  gsd-project-researcher: claude-sonnet-4
  gsd-research-synthesizer: claude-sonnet-4
  gsd-roadmapper: claude-sonnet-4
  gsd-codebase-mapper: claude-sonnet-4
  gsd-debugger: claude-sonnet-4
  gsd-integration-checker: claude-sonnet-4

budget:
  orchestrator: claude-sonnet-4
  gsd-planner: claude-haiku-4
  gsd-executor: claude-haiku-4
  gsd-verifier: claude-haiku-4
  gsd-plan-checker: claude-haiku-4
  gsd-phase-researcher: claude-sonnet-4
  gsd-project-researcher: claude-haiku-4
  gsd-research-synthesizer: claude-haiku-4
  gsd-roadmapp

Note: Budget profile uses Sonnet for research and debugging where quality matters most.

3. Per-Agent Model Mapping

Resolve the model for a specific agent:

resolve(agent: "gsd-executor", profile: "balanced")
-> { model: "claude-sonnet-4", profile: "balanced" }

resolve(agent: "gsd-planner", profile: "quality")
-> { model: "claude-opus-4-6", profile: "quality" }

4. Profile Switching

Switch profiles at runtime:

// Before
{ "profile": "balanced" }

// After set-profile quality
{ "profile": "quality" }

Profile switches take effect on the next agent spawn. Already-running agents are not affected.

5. Model Capability Validation

Ensure selected model supports required agent features:

Validate gsd-executor needs:
  [PASS] Code generation: all models support
  [PASS] Tool use: all models support
  [PASS] Long context: all models support 200k
  [PASS] Structured output: all models support

Validate gsd-debugger needs:
  [PASS] Code analysis: all models support
  [PASS] Reasoning: opus-4-6 > sonnet-4 > haiku-4
  [WARN] Complex debugging may benefit from quality profile

6. Cost Estimation

Estimate cost per profile for a workflow:

Workflow: execute-phase (Phase 72, 2 plans, 7 tasks)
  Agent spawns: 2 executor + 1 verifier = 3 agents
  Estimated tokens per agent: ~50,000 input + ~20,000 output

  quality (opus-4-6 for all):
    Input:  3 * 50k * $0.015/1k = $2.25
    Output: 3 * 20k * $0.075/1k = $4.50
    Total: ~$6.75

  balanced (sonnet-4 for agents):
    Input:  3 * 50k * $0.003/1k = $0.45
    Output: 3 * 20k * $0.015/1k = $0.90
    Total: ~$1.35

  budget (haiku-4 for agents):
    Input:  3 * 50k * $0.00025/1k = $0.04
    Output: 3 * 20k * $0.00125/1k = $0.08
    Total: ~$0.12

Note: Cost estimates are approximate and based on typical token usage patterns.

Tool Use Instructions

Resolving Profile

  1. Use Read to load .planning/config.json
  2. Extract profile field (default to balanced if not set)
  3. Return profile name

Mapping Agent to Model

  1. Resolve active profile
  2. Look up agent name in profile mapping
  3. Return model identifier
  4. If agent not in mapping, use profile default

Switching Profile

  1. Use Read to load current config
  2. Validate new profile name (quality/balanced/budget)
  3. Update profile field
  4. Write updated config (handled by gsd-tools or direct edit)

Cost Estimation

  1. Accept workflow description (agent types and counts)
  2. Map agents to models via active profile
  3. Estimate token usage per agent
  4. Calculate cost based on model pricing
  5. Return cost breakdown

Process Integration

  • All agent-spawning processes call this skill at initialization:
  • new-project.js - Resolve models for 4+ parallel researchers
  • plan-phase.js - Resolve model for planner, plan-checker
  • execute-phase.js - Resolve model for executor, verifier
  • quick.js - Resolve model for planner, executor
  • debug.js - Resolve model for debugger
  • map-codebase.js - Resolve model for 4 parallel mappers
  • iterative-convergence.js - Resolve model per iteration

Output Format

{
  "operation": "resolve|switch|validate|estimate",
  "status": "success|error",
  "profile": "balanced",
  "mapping": {
    "agent": "gsd-executor",
    "model": "claude-sonnet-4"
  },
  "costEstimate": {
    "profile": "balanced",
    "agentCount": 3,
    "estimatedCost": "$1.35",
    "breakdown": {
      "input": "$0.45",
      "output": "$0.90"
    }
  }
}

Configuration

Error Handling

Constraints

  • Only three built-in profiles: quality, balanced, budget
  • Profile changes take effect on next agent spawn only
  • Cost estimates are approximate (actual costs depend on token usage)
  • Custom agent-model overrides in config take precedence over profile defaults
  • Model availability depends on the runtime environment (Claude Code, OpenCode, etc.)
  • Budget profile still uses capable models for critical tasks (research, debugging)

More skills from a5c-ai/babysitter

  • Aadversarial-reviewFresh adversarial code review with binary PASS/FAIL verdicts, evidence citations, and anchoring bias prevention via fresh reviewer spawning.
  • Aagent-boosterWASM-based instant code transforms for simple tasks, achieving 352x speedup over LLM inference with zero cost.
  • Aagent-coordinationCoordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
  • Aagent-dispatch
  • Aanti-driftHierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.
  • Aarchitecture-design
  • Aarchitecture-patternsSystem and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
  • Aassimilate-popular-workflowsThis skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
  • Aaudit-trail
  • AbabysitOrchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
  • Ababysit-babysitter-issuesThis skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
  • Abehavior-contractBug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.

All agent skills → · MCP servers