How is the intent score calculated?

It is a transparent heuristic, not a model call. Sentences gain points for imperative verbs, constraints, formatting rules, examples, and concrete nouns, and lose points for hedging, politeness, and redundancy. It estimates instructional value so you can prioritise what to cut.

Will trimming actually save money?

Yes, on a per-request basis. Input tokens are billed every call, so a prompt used thousands of times benefits directly from every token removed. The tool shows the token count saved as you disable lines.

Is it safe to remove low-scoring sentences?

It is a guide, not a guarantee. Low scores usually mark filler and pleasantries, but a short sentence can still carry a critical constraint. Always re-test the trimmed prompt on real inputs before shipping it.

Does this send my prompt anywhere?

No. All scoring and token estimation run locally in your browser. Nothing is uploaded, so you can safely paste proprietary prompts.

Prompt Length Optimizer

Prompt length optimizer

A prompt you call thousands of times is paying for every token on every request. Most prompts carry dead weight — pleasantries, restated rules, hedging — that adds cost without changing the output. This tool splits your prompt into sentences, scores each one for how much instructional intent it actually carries, and lets you trim the low-value lines while watching the token savings add up live.

How it works

Scoring is a transparent local heuristic, not a hidden model call. Each sentence earns points for the signals that drive model behavior — imperative verbs (“return”, “format”, “never”), explicit constraints, formatting rules, examples, and concrete nouns — and loses points for filler like politeness, hedging, and restated context. The result is a ranked list: high-scoring sentences are load- bearing, low-scoring ones are candidates for the cutting-room floor. Toggle a sentence off and the live token count shows exactly what you saved.

Tips and notes

Trim bottom-up. Start with the lowest scores; those are almost always filler.
Watch for short, high-stakes lines. “Output JSON only” scores modestly by length but is critical — judgement still beats the heuristic.
Re-test after trimming. The optimizer estimates intent; only real inputs confirm the shortened prompt still behaves. Run a few before shipping.
Biggest wins are in high-volume prompts — a system prompt fired on every request is where saved tokens compound into real money.