Theo’s Ultrafast Test: $600 of Usage for Two PR Reviews

A short example illustrates how quickly token costs can rise when using Ultrafast for everyday review work.

TBTheo Browne연사 · Ping Labs
채널
Theo - t3․gg
게시일
2026년 10월 7일
영상
0:29
읽기
1분
슬라이드
1
원문
영어
YouTube에서 열기
스크롤하면 영상이 오른쪽 아래로 작아져 계속 재생됩니다. 자막은 읽기 언어를 따릅니다.
읽기 언어2개 언어로 읽을 수 있음
이 글은 아직 한국어 번역이 없어 영어 원문으로 표시합니다.
요약

30초 요약

Theo Browne describes testing Ultrafast on two pull-request reviews, each involving fewer than 100 lines of code. He reports $600 of combined usage and points to an output price that rose from $50 to $300 per million tokens.

  1. 1An everyday testTheo tried Ultrafast on two pull-request reviews, both under 100 lines.
  2. 2$600 of combined usageHe reports $600 of usage for the two reviews together.
  3. 3A higher output priceHe compares output prices of $50 and $300 per million tokens to explain why the usage value can rise quickly.

핵심 정리

  1. Theo reports $600 of usage across two pull-request reviews, each under 100 lines.
  2. The output price he cites rises from $50 to $300 per million tokens in Ultrafast.
  3. This is one personal example, not a typical or guaranteed cost for reviewing pull requests.
전문

챕터별로 다듬은 전문 읽기

원본 자막만 보기
01

Two small pull requests

Theo describes using Ultrafast for ordinary work. Both reviewed pull requests were under 100 lines.

Ultrafast pricing table
슬라이드 1 / 1Ultrafast pricing tableThe displayed short-context table lists the output rate and other token prices.

When I first tested Ultrafast, I used it for ordinary day-to-day work, including reviewing two pull requests. Both were under 100 lines of code. Together, the two reviews used $600 worth of tokens.

02

The reported usage

He reports $600 of combined usage. He points to a sixfold difference in output-token price.

The output price I am comparing rises from $50 to $300 per million tokens in Ultrafast. That helps explain how a small-looking review can produce such a large usage figure. This is my experience with two reviews, not a general price for every review.

같은 채널의 다른 글

슬라이드 5장38:47EN
Theo - t3․gg· 2026년 10월 28일Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.코딩 에이전트에이전트 엔지니어링AI cost & performance+2
슬라이드 5장36:07EN
Theo - t3․gg· 2026년 10월 27일Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.AI cost & performance코딩 에이전트Inference+1
슬라이드 5장30:37EN
Theo - t3․gg· 2026년 10월 26일Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.Agent skills코딩 에이전트Code review & verification+2
슬라이드 2장0:43EN
Theo - t3․gg· 2026년 10월 23일Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.CybersecuritySoftware engineering
슬라이드 6장29:22EN
Theo - t3․gg· 2026년 10월 22일Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.CybersecurityAI securitySoftware engineering+1
슬라이드 4장31:13EN
Theo - t3․gg· 2026년 10월 20일Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.코딩 에이전트Developer productivityHuman-AI Collaboration+1