Test results
Durable Object Billing Review: Cloudflare Cost: test results
Tested 2026-11-22, skill version 1.0.2 at the time of loading this page. We run every skill on a strong and a weak model before it is listed, and publish both verdicts, including where the weak one fails.
Verdicts
- Date
- 2026-11-22
- Strong · claude-sonnet-5-5 (Claude Code alias "sonnet")
- Right on all 16 setups on the 1.0.2 bytes, read by hand. It named the AbortSignal.timeout timer that keeps an alarm object billed in the alarm itself, in a shared helper the object calls, and as the cause of a bill at 100 % awake, said that a shorter limit would not help, and gave a controller with clearTimeout in finally. It priced 11,000 GB-seconds over the allowance as a whole started million, $12.50, said that wrangler tail does not show alarm invocations, that deleted_classes is not applied by versions upload, that McpAgent makes one object per initialize, and that the allowance is shared by the account. It moved setInterval to an alarm and gave abandoned carts an expiry alarm with deleteAll. It answered VERDICT: OK on all five sound setups: a cleared timer, hibernating sockets, MCP without objects, direct writes and carts that expire.
- Weak · claude-haiku-5-5 (Claude Code alias "haiku")
- Right on 14 of 16 on the 1.0.2 bytes, read by hand. It named the uncleared AbortSignal.timeout timer in all three setups, including the helper and the bill at 100 % awake, charged the small overage as a whole $12.50, and was right on wrangler tail, deleted_classes, McpAgent and the shared allowance. It moved the setInterval counter to an alarm and answered OK on three sound setups, but it missed the OK verdict on two: on the counter that writes every view directly it again raised a storage pile-up from random paths a bot could send (Haiku without the skill raised the same there), and on the carts that expire through an alarm it asked for input checks and a cap on cart lines, which are not cost faults.
With and without the skill
Tested 2026-11-22.
| Sonnet | Haiku | |||
|---|---|---|---|---|
| with | without | with | without | |
| Setups answered right (16 setups) | 16/16 | 12/16 | 14/16 | 10/16 |
Same request and checks on both sides. Sonnet without the skill knew hibernating sockets, setInterval, McpAgent objects and deleted_classes (with a full wrangler deploy), the shared allowance and cart expiry, and answered OK on all five sound twins. It missed two measured facts about money: a limit from AbortSignal.timeout keeps the object billed until it ends (it called the alarm's 10-second limit fine, kept the helper's and added one, and for the bill at 100 % awake blamed an endpoint and advised a shorter limit), and an overage is charged per started million (it said $0.14, the invoice $12.50). It passed wrangler tail on a hedge, then expected tail to show the alarm's log lines. Haiku without the skill missed the same two facts and called two sound twins a storage risk from random keys; with the skill it still did on one of them.
Same cases and the same checks with and without the skill. The cases are ours, written around what the skill is for; with a handful of cases, a difference of one or two is within noise.
Note
Sixteen setups written by us: four code reviews with a cost fault (an alarm with AbortSignal.timeout, the same limit hidden in a helper, setInterval on a counter, carts never deleted), five sound twins of them, and seven questions about a bill or a symptom (an object awake all month, storage growing under McpAgent, three Workers against one allowance, one Worker under it, no alarms in wrangler tail, 11,000 GB-seconds over, deleted_classes through versions upload). Each answer is scored by code on the concept in any words: the verdict line, the fix (AbortController and clearTimeout, an alarm, deleteAll, a handler without sessions) and the figure or fact asked for; a sound twin passes only with VERDICT: OK or nothing must change. Price units and the account allowance are from the vendor's pricing page. Owner-measured on 19 and 20 November 2026 and not re-checked here: a one-minute alarm billed for about 61 seconds a wake while its calls took 2, 10.82 thousand GB-seconds over billed at $12.50, 91,032 McpAgent objects and 11.77 GB in seven weeks, no alarm invocations in wrangler tail, deleted_classes applied only by a full wrangler deploy. Checks widened after reading the answers, for both sides: VERDICT: OK followed by its gloss and a plain nothing must change count as OK; $12.50 named as the rate is not a wrong charge; on the setInterval counter, writing each view directly in fetch counts as a fix beside an alarm. Three inputs were fixed and run again without the skill before it was written: the sound timer twin and its faulty pair, and the wrangler tail question. After the first run the skill's code example became an indented block instead of a fenced one, for the catalog's safety gate; the side with the skill was then run again in full on those final bytes, and the numbers here are from that run (Sonnet 16 of 16 as before, Haiku 15 of 16 instead of 14). One run per model and setup. Version 1.0.2, 22 November 2026: two sentences were reworded so that no published post on our blog shares a run of five words with the file; the side with the skill was run again in full on those bytes. One check was widened for both sides after reading the answers: a sentence that describes sound code as using a controller, not AbortSignal.timeout, is not advice to use AbortSignal.timeout (Sonnet wrote it on the cleared timer and was right). With that: Sonnet 16 of 16, Haiku 14 of 16. The side without the skill re-scored with the same checks: unchanged, 12 and 10 of 16.
What was not measured
- Models other than the two named above were not run.
- Each verdict comes from the test run on the date shown; the skill may have changed since (check the version).
- Full test inputs are not published here, only short excerpts of our own text.
- Results on your own texts, languages and domains can differ.
Back to Durable Object Billing Review: Cloudflare Cost · Card (JSON)