Two catalog files. Exact SKU matches. Clear exceptions. This synthetic demonstration shows a small CSV reconciliation with FreelanceAgent: a 3-row master catalog and a 3-row reference file, listed in different orders. The agreed rules: match sku to code exactly; update only price from cost and stock from quantity. Keep unmatched master rows and report unused reference rows. What changed: • 00123: price 12.50 → 12.70; stock 5 → 15. • B02: price 00.90 → 00.95; stock 3 → 0. • B03: no reference match, so the entire row stayed unchanged. • EXTRA: reference-only SKU, reported rather than appended. Result: 2 matched rows, 4 updated cells, 1 unmatched master row and 1 unused reference row. All 3 master rows kept their original order. The key 00123 kept its leading zeros; names and all other cells were preserved. Independent QA rebuilt the match relation and compared every output cell. All 13 checks passed, including exceptions, untouched cells and the output hash. The attached visual shows the actual saved inputs and result. This is an AI-assisted synthetic demonstration, not client work or a performance benchmark. The published service supports two UTF-8 CSV files with an agreed shared dialect, or two flat JSON arrays with string values. Matching uses unique, nonempty, case-sensitive string SKUs; no fuzzy matching or live system updates. Need to reconcile two catalog exports? Share the file formats and which fields may change through the service. Scope and pricing are agreed before work: https://contra.com/s/A73oAkkc-csvjson-sku-reconciliation-or-exact-matching-and-qa #CSV #JSON #DataReconciliation

Same app. Same model. Same spec. Built with Angular, it cost $4.97 per run. Built with Hono + htmx, $2.67. The framework you pick is now a line on your AI bill.

Nobody budgets for this yet. Here is the data.

Nolan Lawson (engineer at Socket, the PouchDB maintainer) had Claude Opus 5.5 build the same small Pokémon app 12 times over, once per framework, 5 runs each (3 for Angular), medians reported.

Every build had to pass the same spec suite.

→ Cheapest: Hono + htmx, $2.67, 4.26M tokens, 1,370 lines, 8.6 min → Astro $2.76 · Nuxt $2.82 · plain Vite $2.98 → Next.js $3.14 · React Router $3.81 · SvelteKit $4.28 → Most expensive: Angular, $4.97, 9.76M tokens, 2,009 lines, 17.2 min → Source: nolanlawson.com, Oct 28 2026. Two Angular runs failed the spec and were counted as failures.

The gap is not the model. It is the ceremony.

Angular made the agent write 47% more code for the same features. More code costs tokens twice: once to write it, once to re-read it on the next change.

Plain Vite was not the cheapest. No framework means no conventions, so the agent invents its own, and that costs tokens too.

The cheap column was also the fast column. Astro, Hono + htmx and Lit all scored 100 on mobile Lighthouse with almost no JavaScript shipped.

Why it works that way: An agent pays for every file it opens. Config, boilerplate, framework docs, a second read after each error. Less ceremony is fewer pages before the first useful line.

Call it the ceremony tax: everything your stack makes the agent type before it ships a feature.

I run a one-person company on AI agents. Most of my code is written by them now, and I watch tokens per task the way I used to watch cloud bills. The same feature costs me very different amounts depending on which codebase the agent is standing in.

If agents write your code, the framework is no longer a developer-experience choice. It is a unit cost.

Rule 1: Measure tokens per task, not per month. A monthly bill hides which stack is burning it.

Rule 2: Pick the stack the agent types least in. Fewer lines written today is fewer lines re-read tomorrow.

Rule 3: Cheap must still pass the spec. Every run here cleared the same tests and Lighthouse; cheaper and better landed in the same column.

One small app, one model, one author's benchmark, and the author says so himself. Treat it as a pattern, not a law. The direction matches what I see every day.

Angular is good software. I mean that. It was built for teams of humans.

AI did not make frameworks free. It put a price on them.

For an agent-built app, would you go Minimal or Batteries? One word is enough. 👇