Thinksy EngineeringEngineer usage detail
FY2027 · Feb 2026 – Jan 2027Data through Oct 2026
← Engineering Effectiveness report
Growth & SEO · Sam Okafor

Jordan

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
$2,407
241 sessions · $10 each
Savings opportunity
$1,005
42% of spend, at list price
Practices on target
2 of 7
Focus: Opus on routine work, rtk coverage
Cache hit rate
79%
Team 79% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$1,005 of $2,407 spend

Right-size models$402Improve prompt caching$358Keep context lean$209Route commands through rtk$36

What to change

Largest saving first

  1. Right-size models$402

    81% of routine spend ran on Opus: code research $516 of $639, documentation $305 of $380, ops $24 of $29, presentation $133 of $164.

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

  2. Improve prompt caching$358

    Cache hit rate 79% 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.

  3. Keep context lean$209

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

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

  4. Route commands through rtk$36

    61% of 2,172 Bash calls ran through rtk; 3.8M 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 Growth & SEO and the organization

PracticeJordanTeamOrgTargetRecommendation
rtk coverage61%Needs attention62%56%≥ 80% of Bash callsInstall the rtk hook so test, build, git and search commands return compact output.
Knowledge MCP use
9 findings saved back
30%Needs attention30%30%≥ 40% of sessionsSearch the knowledge MCP before re-researching a codebase, and save findings back with remember.
Cache hit rate79%Needs attention79%82%≥ 85% of inputKeep CLAUDE.md and tool lists stable, avoid mid-session model switches, and resume sessions instead of restarting.
Context past 100K25%Needs attention18%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 work81%Off target58%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents44%On target47%50%≥ 30% of sessionsOn target
Tool error rate3.0%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––60%Off target28%Off target86%Off target10%Off target$92
Mar 2026––61%Off target25%Needs attention86%Off target24%Needs attention$109
Apr 2026––69%Off target24%Needs attention86%Off target29%Needs attention$64
May 202626%Off target–69%Off target24%Needs attention84%Off target30%On target$261
Jun 202650%Needs attention13%Off target77%Needs attention23%Needs attention83%Off target52%On target$100
Jul 202667%Needs attention21%Needs attention80%Needs attention24%Needs attention79%Off target47%On target$121
Aug 202666%Needs attention33%Needs attention83%Needs attention27%Off target78%Off target46%On target$109
Sep 202669%Needs attention39%Needs attention86%On target25%Needs attention76%Off target57%On target$96
Oct 202676%Needs attention39%Needs attention87%On target23%Needs attention75%Off target60%On target$54
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$200$400$600$118Feb$184Mar$117Apr$452May$240Jun$353Jul$350Aug$370Sep$223Oct

AI spend by session type

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

Harness$465Freeform$341Code research$639Documentation$380Ideation$388Ops$29Presentation$164

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.53,30814M164.4M11.4M4.7M$239
Opus 55,36229.4M251.2M17.9M7.6M$574
Opus 4.83,48130.5M158.9M12.1M5.3M$439
Opus 4.64,59674.5M183.4M16.5M7.3M$749
Opus 4.51753.5M6.2M621K248K$31
Sonnet 5.58454M48M3.3M1.4M$36
Sonnet 52,18213.1M105.7M7.6M3.4M$150
Sonnet 4.61,22217M51.3M4.4M1.8M$110
Sonnet 4.5791.7M2.9M292K107K$9
Haiku 5.51,8067.9M96.7M6.7M2.3M$4
Haiku 4.51,61915.8M79.9M6.1M2.5M$44
GPT Realtime (meetings)2332.4M11M854K365K$23
Total24,908213.8M1159.8M87.7M36.9M$2,407

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