Muse Wonder
Muse Wonder · xhigh, showing maintainability. Results for all tested efforts are available below.
Maintainability57
Muse Wonder · xhigh
- Backend engineering
- 72
- Frontend interaction
- 81
- Knowledge & reasoning
- 80
- Visual aesthetics
- 73
- Maintainability
- 57
- Evaluation time
- —
- Cost
- —
Maintainability · Evaluation time & API cost
Results by reasoning effort
Swipe to see all results →
| Model / effort | Overall | Backend engineering | Frontend interaction | Knowledge & reasoning | Visual aesthetics | Maintainability | Total eval. time | Total ref. cost | Compare |
|---|---|---|---|---|---|---|---|---|---|
| 65.85 | 67 | 75 | 60 | 68 | 59 | 9m 50s | $2.49 | ||
| 73.60 | 72 | 74 | 80 | 68 | 59 | 19m 41s | $3.30 | ||
| 75.65 | 72 | 81 | 80 | 73 | 57 | 30m 45s | $5.11 | ||
| 80.30 | 78 | 80 | 90 | 73 | 59 | 40m 8s | $6.78 |
Score breakdown
- Overall score
- 75.65
- Evaluation time
- 30m 45s
- Cost
- $5.11
Code readability, organization and the cost of change.
Semantic clarity15 / 20
Naming, explicit responsibilities and readability.
Control-flow organization19 / 20
Execution paths, responsibility boundaries and logical structure.
Locality of changes15 / 20
The scope of rule changes and duplicated maintenance.
State and lifecycle17 / 20
State ownership, cleanup and lifecycle management.
Implementation economy17 / 20
Implementation complexity, useful abstractions and redundancy.
Subscores retain their original scale; the axis score uses a consistent conversion.
What changes with higher reasoning effort
Compare maintainability scores, cost, and time across neighboring tested efforts.
high xhigh
- Maintainability
- −2.0 pts 59.00 → 57.00
- Cost
- — — → —
- Evaluation time
- — — → —
Data snapshot published · 11/13/2026Scoring & cost notes