Menu

Why cumulative input cost grows quadratically when an agent resends its history, and a pre-commit gate that stops known leak patterns
📰

Why cumulative input cost grows quadratically when an agent resends its history, and a pre-commit gate that stops known leak patterns

DEV Community: security·ZEUS LAB·about 7 hours ago
#1f7qkxSB
#devtosecurity#devto#dev#self#name
Reading 0:00
15s threshold

An agent job that costs cents suddenly costs dollars on the day it runs long. A repository or ZIP you published turns out to contain a path with your login name, or a secret key. Both are found after the fact.

Check yours in 30 seconds → https://zero-trace-ship-kit.zeus-lab-global.workers.dev/

Drop a folder or a ZIP before you publish it and every trace is listed on the spot. It runs entirely in your browser and makes no network requests.

What this covers

Why the cost of an LLM agent has a cumulative input cost that grows quadratically with the step count when the history is resent on every step, shown with a formula and calculated values.

Why budget alerts don't stop anything, and a minimal guard that prices a call before it runs.

A pre-commit / pre-push gate, written with the Python standard library only, that blocks personal traces (home paths with a login name, secret keys, e-mail addresses, EXIF, OS residue) from reaching a public repo or a distributable ZIP, and how it was verified.

Every dollar…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.