Thinksy EngineeringEngineer usage detail
FY2027 · Feb 2026 – Jan 2027Data through Oct 2026
← Engineering Effectiveness report
Video Rendering · Jamie Park

Devon

Lead engineer · AI usage, harness practices and where spend could have gone further.

Demonstration report. This engineer and their usage are synthetic.

This page is for the engineer and their manager to find cheaper defaults and harness fixes. It is never used to rank people.

Period
01

Summary

FY2027 to date

AI spend
$3,203
200 sessions · $16 each
Savings opportunity
$1,038
32% of spend, at list price
Practices on target
2 of 7
Focus: rtk coverage, Context past 100K
Cache hit rate
81%
Team 82% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$1,038 of $3,203 spend

Improve prompt caching$482Keep context lean$349Right-size models$162Route commands through rtk$45

What to change

Largest saving first

  1. Improve prompt caching$482

    Cache hit rate 81% against an 85% target.

    Keep stable context at the front of prompts and avoid switching models mid-session, so 85% of input reads from cache.

  2. Keep context lean$349

    31% of input tokens were past 100K of context.

    Compact or /clear between tasks instead of carrying more than 100K tokens of context.

  3. Right-size models$162

    43% of routine spend ran on Opus: code research $237 of $541, documentation $8 of $15, ops $136 of $329, presentation $14 of $30.

    Run docs, decks, ops and read-only research on Sonnet instead of Opus.

  4. Route commands through rtk$45

    1% of 1,616 Bash calls ran through rtk; 4.2M tokens of command output went into context.

    rtk compacts test, build, git and search output before it reaches the model (about 70% smaller).

03

Harness practices

Compared with Video Rendering and the organization

PracticeDevonTeamOrgTargetRecommendation
rtk coverage1%Off target2%56%≥ 80% of Bash callsInstall the rtk hook so test, build, git and search commands return compact output.
Knowledge MCP use
5 findings saved back
28%Needs attention28%30%≥ 40% of sessionsSearch the knowledge MCP before re-researching a codebase, and save findings back with remember.
Cache hit rate81%Needs attention82%82%≥ 85% of inputKeep CLAUDE.md and tool lists stable, avoid mid-session model switches, and resume sessions instead of restarting.
Context past 100K31%Off target17%10%≤ 10% of inputCompact or /clear between tasks; hand broad searches to subagents so their reads stay out of the main context.
Opus on routine work43%Needs attention43%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents48%On target48%50%≥ 30% of sessionsOn target
Tool error rate2.7%On target3.0%3.0%≤ 4% of tool callsOn target

Practices by month

Is the engineer moving toward the targets?

MonthrtkKnowledgeCacheContextModel fitSubagentsSavings opportunity
Feb 2026––57%Off target30%Off target62%Off target26%Needs attention$65
Mar 2026––61%Off target30%Off target62%Off target23%Needs attention$52
Apr 2026––64%Off target32%Off target62%Off target36%On target$75
May 20264%Off target–68%Off target29%Off target55%Off target43%On target$145
Jun 20265%Off target11%Off target72%Needs attention32%Off target53%Off target42%On target$317
Jul 20260%Off target26%Needs attention81%Needs attention29%Off target40%Needs attention37%On target$99
Aug 20261%Off target34%Needs attention80%Needs attention29%Off target38%Needs attention60%On target$125
Sep 20261%Off target39%Needs attention83%Needs attention33%Off target30%Needs attention42%On target$69
Oct 20260%Off target32%Needs attention88%On target31%Off target27%Needs attention70%On target$90
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$200$400$600$800$108Feb$90Mar$150Apr$260May$777Jun$391Jul$403Aug$327Sep$697Oct

AI spend by session type

Routine types (documentation, presentation, ops, code research) rarely need Opus

Harness$639Freeform$1,324Code research$541Documentation$15Ideation$324Ops$329Presentation$30

Tokens by model

Cache reads are billed at a fraction of uncached input; a high share is what good caching looks like

ModelRequestsUncached inputCache readsCache writesOutputSpend
Opus 5.55,91522.2M290M19.9M7.8M$403
Opus 53,41726.5M171.7M12.6M5.4M$432
Opus 4.84,93758.4M236.4M18.8M7.5M$714
Opus 4.63,11552M120.9M11M4.5M$502
Opus 4.51273.1M4.6M490K194K$26
Sonnet 5.57,58526.8M366.8M25.1M9.3M$246
Sonnet 56,02541.7M282.1M20.7M8.4M$413
Sonnet 4.63,40747.9M144M12.3M5M$308
Sonnet 4.51202.7M4.1M435K143K$13
Haiku 5.57,52426.7M376.9M25.8M11.8M$16
Haiku 4.54,37741.4M204M15.7M6M$111
GPT Realtime (meetings)2611.7M11M812K311K$19
Total46,810351.1M2212.5M163.6M66.3M$3,203

Methodology

  • Spend and tokens come from LiteLLM gateway logs and imported agent session history, priced at API list rates.
  • Savings are estimates: routine Opus work repriced at the Sonnet available at the time; uncached input moved to cache reads up to an 85% hit rate; rtk removing 70% of unfiltered command output, which stays in context for about half the session's remaining turns; and 50% of input past 100K context avoided by compacting. Levers overlap, so the total is an upper bound.
  • rtk and the knowledge MCP are scored from their rollout (rtk May 2026, knowledge MCP Jun 2026).
  • Generated Oct 20, 2026, 7:46 AM.
Engineer Usage Detail (demo) · Thomas Tucker