Agent skill
agent-model-selection
Guidelines for selecting appropriate AI model (Sonnet vs Haiku) based on task complexity, ensuring cost efficiency while maintaining quality. Use when assigning work.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/agent-model-selection
SKILL.md
Agent Model Selection
Instructions
Core decision
Sonnet: Complex reasoning, architecture, security (2+ criteria) Haiku: Defined rules, repetitive tasks, simple commands (~95% cheaper)
Selection criteria
Use Sonnet if 2+ apply:
- Logical reasoning and trade-off analysis
- Architecture/design decisions
- Semantic/intent analysis
- Problem diagnosis and strategy
- Multi-component interaction
- Security/performance analysis
Use Haiku if dominant:
- Following defined rules/templates
- Repetitive mechanical tasks
- Command execution and collection
- Simple CRUD operations
- Format validation
Decision flowchart
Architecture/design? → YES → Sonnet
Multiple options? → YES → Sonnet
Security/performance? → YES → Sonnet
Defined rules only? → YES → Haiku
Detailed guide? → YES → Haiku
Large delegated? → YES → Sonnet
Simple commands? → YES → Haiku
Default: Sonnet (quality first)
Example
Task: Add validation logic
→ Analysis: Complex rules + security + error handling
→ Decision: Sonnet (3 criteria met)
Task: Add tags to files
→ Analysis: Template exists, repetitive
→ Decision: Haiku (rule-following)
For detailed criteria, see reference.md For more examples, see examples.md
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?