Why repeatable agents consume so many tokens
A multi-step agent repeatedly loads instructions, tool schemas, conversation history, and intermediate tool results. It then spends tokens deciding what to do next—even when yesterday's successful run already established the procedure. Context compaction and cheaper models lower the unit price, but they do not remove repeated reasoning from the hot path.
Compile the procedure, preserve the judgment
Rote classifies a skill into five explicit node kinds: pure functions, external calls, LLM judges, bounded agent loops, and human approval gates. Fixed validation and routing become code. Ambiguous classification can remain a typed LLM judge. The result is a reviewable pipeline rather than an opaque prompt loop.
Evidence for the mechanism
Anthropic documented an MCP code-execution example that reduced token use from 150,000 to 2,000 by filtering and composing tool results in code instead of passing everything through the model. Independent Compiled AI research reports 57× fewer tokens at 1,000 transactions for a compiled implementation. These are not universal Rote benchmarks; they show why removing inference from repeated work changes the economics.
Independent compiled implementation: 57× fewer tokens at 1,000 transactions
Evidence describes specific studies—not a universal Rote guarantee.
Measure your workflow before rollout
Run rote eval to generate an assumption-visible scorecard for tokens, cost, latency, and roteness. Use rote eval --run when the real tools and runtime are available to measure both implementations. Publish model names, pricing dates, cold and warm latency, p50 and p95, success rate, and run-to-run variance.
Frequently asked questions
How does Rote reduce AI agent token costs?
Rote moves deterministic logic and fixed tool orchestration out of the model loop. The model is called only for nodes explicitly classified as requiring judgment, so repeated execution does not pay to re-read and re-derive the entire procedure.
Should I switch to a cheaper model instead?
A cheaper model reduces the price of every remaining token but leaves the architecture unchanged. For a proven repeatable workflow, first remove model calls that code can perform exactly; then choose the best model for the smaller set of judgment steps.
When should I graduate a skill?
Keep one-off exploration in an agent. Graduate a skill after the procedure is proven, repeats often, and needs lower cost, faster execution, regression tests, explicit approvals, or reliable retries.
Graduate a workflow
Inspect the open-source CLI or run a graduation in Rote Cloud.