Snazzyham's AI Benchmark

Models tested against my personal workflows, rather than an arbitrary benchmark.

Latest result per task for each model. Full stack averages FS1 and FS2, and Lead averages L1 and L2; each needs both tasks; with one missing it shows as incomplete. Click a row for task scores, dates and source runs; click a column header to sort.

The effective token rate sets how much you value time saved, and the Best value pick in each table is recommended on that basis. At a lower rate, price counts for more, so cheaper models win even when they are slower. At a higher rate, speed counts for more, so faster models win even when they cost more.

Digest

Compress a 3,853-line business-rule spec and a 723-line client audit, in under 40 lines each.

What the tasks check
D1 checks a business-rule specification is compressed without losing conditions
D2 checks a client audit is compressed without losing critical issues
ModelScoreCostEffectiveTimeTokensRun

Plan

Name every file a known change has to touch. The real fixes touched 25 and 19 files.

What the tasks check
P1 checks a plan names every file affected by the icon-system change
P2 checks a plan names every file affected by the materialised-order-cost change
ModelScoreCostEffectiveTimeTokensRun

Best value: the paid model within 8 points of the best paid score, scoring 75 or above, with the lowest cost once its time is charged at the rate set above.

Frontend dev

Ship a CMS section end to end, and apply a design batch that then gets corrected mid-task.

What the tasks check
B1 checks a CMS section is shipped end to end and correctly registered
B2 checks a design batch is applied and corrected after a steering request
ModelScoreCostEffectiveTimeTokensRun

Best value: the paid model within 8 points of the best paid score, scoring 75 or above, with the lowest cost once its time is charged at the rate set above.

Full stack

Build a slice of a shipped warehouse feature (FS1), and repair a workout log's history paging and monthly totals (FS2).

What the tasks check
FS1 checks a warehouse import-tracking feature against hidden tests on a fresh database
FS2 checks a workout log loads its full history in pages and reports true monthly totals
ModelScoreCostEffectiveTimeTokensRun

Best value: the paid model within 8 points of the best paid score, scoring 75 or above, with the lowest cost once its time is charged at the rate set above.

CLI development

Build a terminal download dashboard, with a fixed recovery follow-up only if the first saved implementation does not already satisfy the complete checklist.

What the tasks check
CLI1 checks saved Go changes against a shipped download dashboard and recovery fix, with conditional feedback
ModelScoreCostEffectiveTimeTokensRun

Best value: the paid model within 8 points of the best paid score, scoring 75 or above, with the lowest cost once its time is charged at the rate set above.

Ops

Make a slow, leaky Astro + Sanity Dockerfile fast and safe, and fix a broken server from a copy of its files.

What the tasks check
O1 checks a Dockerfile builds a small, cache-friendly image without leaking the CMS token
O2 checks a broken server snapshot is repaired without weakening its protection
ModelScoreCostEffectiveTimeTokensRun

Best value: the paid model within 8 points of the best paid score, scoring 75 or above, with the lowest cost once its time is charged at the rate set above.

Review

Three storefront-header and cart/menu diffs: the header change with two injected requirement violations, the shipped header with two unmet requirements, and a mobile fix with a menu-view mismatch.

What the tasks check
R1 checks a storefront-header diff for the two injected requirement violations
R2 checks the shipped header against its desktop search width and gap requirements
R3 checks a mobile navigation fix for a mismatched menu-view name
ModelScoreCostEffectiveTimeTokensRun

Best value: the paid model within 8 points of the best paid score, scoring 75 or above, with the lowest cost once its time is charged at the rate set above.

Lead

Run a scripted client conversation as the orchestrator: a vague brief that changes midway and a question that needs a lookup (L1), then a pure recommendation followed by a lookup (L2). Scout, digest and build are pinned, so only the lead changes.

What the tasks check
L1 checks the lead routes work to the right helper, briefs it, and ships a changed discount rule
L2 checks the lead answers a design question itself and delegates only the lookup
ModelScoreCostEffectiveTimeTokensRun