Profile spend by call class

Find where the money actually goes before moving anything.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Profile my agent's model spend. Instrument every model call with: call class (main-loop reasoning, compaction summary, memory extraction, classification/routing, repair, sub-agent, embedding), model, tokens in/out, and computed cost. Run a representative day of tasks (or replay recent transcripts through the accounting). Produce the spend breakdown: cost share per class, average call size per class, and the top-3 cost concentrations. Typical finding worth checking: auxiliary calls (summaries, classifications) making up a large cost share while needing far less capability than they get.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A spend breakdown by call class with concentrations identified.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Every call site tagged with a classCosts computed from real token countsTop concentrations quantified

Do not continue if…

! Premium models summarizing tool output at 20x the needed cost
! Cheap models silently degrading main-task quality with no eval to notice
! Routing logic duplicated across call sites, drifting independently
! No escalation, so cheap-tier failures just become task failures

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

Call sites are untagged and unmeasurable. Add the class tag to the single model-client wrapper (create one if calls are scattered - that wrapper is also where routing will live).