UK-based independent AI efficiency projectEvidence before claims ยท 2026

Building AI Tools We Needed for Real Workflow Questions

A question is mapped to a tool input, transparent output and explicit limitation; no adoption or impact metric appears.

Written by

Token Optimisation

in

,

Classification: LIVE tool capabilities are inspectable; usage, adoption and outcome impact are UNKNOWN.

Workflow Tools: Question โ†’ Inputs โ†’ Transparent OutputLIVE CAPABILITY MAP ยท ADOPTION UNKNOWN. DEFINE QUESTION โ†’ ENTER LOCAL INPUTS โ†’ REVIEW RESULT โ†’ CHECK LIMITATIONS. The three utility pages exist; usage, adoption, and outcome impact are unknown.LIVE CAPABILITY MAP ยท ADOPTION UNKNOWN1DEFINE QUESTION2ENTER LOCAL INPUTS3REVIEW RESULT4CHECK LIMITATIONSAgent operating-rules builder ยท Token optimisation rules builder
LIVE CAPABILITY MAP ยท ADOPTION UNKNOWN. The three utility pages exist; usage, adoption, and outcome impact are unknown.

The tools were built around recurring questions in Token Optimisation’s practical workflow work: what an agent should do when state or access changes, which context rules are selected, and how a cost scenario should expose assumptions.

Three narrow jobs, three separate pages

What they do not prove

Interactive output can be checked in the browser, but the existence of a tool does not prove token savings, better jobs, adoption or reduced review time. Those claims require usage evidence and a comparable acceptance test.

Each page explains its inputs and limitations. Calculations run locally and do not call an AI, pricing or FX service. API rates carry source links and dates; the Pro 100 charge is user-recorded, not a subscription token rate.

Start from the tools directory or the scoped observations in request measurement and recovery signals.