Claude Opus 5.5 in OpenCode 1.18.32
skills off
Zoom, inline player and more ways to view
Wall time 35m 51sCost $8.51 reported
Review
No verdict yet.
The full review
OK. Finished on its own after 35.9 min and produced brown_pelican.svg.
Scores
AI judge
Not scored
No rubric for this prompt
Visitor votes and reviewer grades are not available yet.
- AI judge
- AI judge: the test runner (model claude-opus-5-5), scoring by visual review of the 1600 px render against the pre-registered rubric. No AI-judge score exists for this result: there is no rubric for this prompt, so no score is shown and none is made up.
- Visitors
- Public voting with a blind reveal is coming: you score the output first, then see the other scores.
- Reviewer
- The reviewer's own grade appears here once it is added.
Scores compare results for the same prompt only. AI-judge boards rank runs within one prompt, equal totals sharing a rank; scores from different prompts are never averaged.
Downloads
Files actually published for this run. Original output, site-made previews and post-run conversions are labelled separately.
The exact prompt
agentic harness (save the file; self-render allowed), 561 characters. Every result for this prompt
Generate an SVG of a California brown pelican riding a bicycle. The bicycle must have spokes and a correctly shaped bicycle frame. The pelican must have its characteristic large pouch, and there should be a clear indication of feathers. The pelican must be clearly pedaling the bicycle. The image should show the full breeding plumage of the California brown pelican. Save it as brown_pelican.svg in the current directory. You may render and inspect your own output (headless chromium is available at /usr/bin/chromium) and iterate on your own before finishing.
How it was made
Step by step
The prompt, every agent turn and tool call (tool name and a one-line summary; inputs and outputs are not shown), then the final message. The full transcript is 9.7 MB; it is published as a scrubbed, compressed download rather than shown on the page.
Show all 168 steps
Loading the timeline…
Download the full transcript OpenCode session export, 114 KB, gzip. Scrubbed: anything that looks like a key, token, e-mail address or phone number is replaced, and account details and the test machine's file paths are removed.
Cost breakdown
Headline cost $8.51, as reported by OpenCode (its own bill for the run). The list-price estimate from the token counts is $8.51.
| Tokens by type | Tokens | $ per 1M | Cost |
|---|---|---|---|
| Input (uncached) | 164 | $4.00 | $0.0007 |
| Cache write | 328,677 | $5.00 | $1.6434 |
| Cache read | 14,456,974 | $0.20 | $2.8914 |
| Output | 62,566 | $20.00 | $1.2513 |
| reasoning | 136,140 | $20.00 | $2.7228 |
- Total computed from tokens
- $8.5096
- Total reported by the harness
- $8.5096
- Difference
- computed 5.7868 vs harness 8.5096
Tokens from OpenCode per-message usage; harness total = sum of OpenCode per-message cost. OpenCode reports reasoning separately; both bill at the output rate (output line here = output only, see reasoning).
Prices: Project price table (vendor list prices); cache write 1.25x input, 2026-09-22.
Run notes
- A well-known benchmark author's detailed pelican prompt, verbatim from the image alt text of the post (his own comment in brackets after it left out).
- Mode: interactive TUI in tmux (160x48), inside bubblewrap sandbox
- Isolation: bwrap: private /tmp and /run, private PID ns; only this run dir, harness binaries (ro), opencode config, /usr, /etc bound; HOME/TMPDIR/XDG data private; the project files and other runs not mounted