# Agent Cost Levers: cut cost per solved task without cutting quality

> A Markdown pack that measures what your coding agent spends per finished task, then works five levers one at a time: thinking depth, context curation, direct tool routing, cache and reuse, and a verified stop. Includes a baseline sheet, a rules block and 10 prompts.

- URL: https://paperchasewebb.ai/bots/marketplace/items/agent-cost-levers-cut-cost-per-solved-task/
- Type: Prompt pack
- Category: Vibe coding
- By: PaperChaseWebb
- Works with: Claude Code, Codex, Cursor (named in the listing); Plain .md
- Price: $24 USD
- Difficulty: Intermediate
- Setup time: 45 min
- Time to result: A baseline and your first lever tested in one afternoon
- Format: Markdown (.md) file, agent-cost-levers-cut-cost-per-solved-task.md
- Version: 1.0, updated 2026-10-26
- License: Personal and commercial use on your own projects and your team's. Do not resell or republish this pack.

## What you end up with

You know what a solved task costs today, you keep only the changes that lower it while your checks still pass, and any savings number you report can be checked.

## What you get

- 10 sections in one .md file
- The cost per solved task formula and a baseline sheet
- Five levers, each with how to pull it and what to watch
- A claim discipline checklist for reporting savings
- A rules block for CLAUDE.md, AGENTS.md or a Cursor rule
- 10 prompts to measure, diagnose and apply the levers

## Who it is for

Builders whose agent bills keep climbing and who want a measured way to bring them down without trading away quality.

## Tools needed

- Claude Code: reports session usage and reads CLAUDE.md
- Codex: reports session usage and reads AGENTS.md
- Cursor: reads the project rule
- You need: A coding agent such as Claude Code, Codex or Cursor
- You need: Access to its usage numbers
- You need: A repo with real tasks to measure

Cost to run: Free. Uses the agent and usage reports you already have.

## Sample prompt: Find the carried weight (Claude Code, Codex, Cursor)

```
Review this session transcript [path]. List every large block of output (over 100 lines) that stayed in context after it stopped being useful, with the turn it appeared and the last turn it was needed.
```

Most long-session overspend shows up here first.

## Sample prompt: Compare two runs honestly (Claude Code, Codex, Cursor)

```
Here are the baseline and the new run for the same ten tasks [paste both]. Compute cost per solved task and the pass count for each, and the change.
If the pass count dropped, say so first. Do not call anything a saving if quality fell.
```

Run it after every lever you try.

## Free preview of agent-cost-levers-cut-cost-per-solved-task.md

````markdown
# Agent Cost Levers: cut cost per solved task without cutting quality

A PaperChaseWebb pack, version 1.0. Written for Claude Code, Codex and Cursor, and plain Markdown, so the measuring sheet, the rules block and the prompts work with any agent harness that logs its usage.

Most advice on agent costs starts with the model price. That is the one number you control least. What you do control is how the agent spends its turns: how hard it thinks on easy steps, how much stale output it carries, how often it asks the model for something a command could answer, what it recomputes, and whether it knows when to stop. This pack turns those five habits into a measured routine. You record a baseline, pull one lever at a time, and keep only the changes that lower cost per solved task while the pass rate holds.

It comes from our own usage audits plus one public benchmark write-up we checked against its primary source and rebuilt in our own words. The source is credited by link in the Sources section.

## What is inside

| Section | What it is for |
|---|---|
| 1. The number to watch | Why cost per solved task beats tokens per call, and how to set up a ten-task baseline |
| 2. Lever one: thinking depth | Match reasoning effort to the step instead of running every step at maximum |
| 3. Lever two: context curation | Keep the working context small and current as a session grows |
| 4. Lever three: direct tool routing | Send deterministic questions to commands, not to the model |
| 5. Lever four: cache and reuse | Keep a stable prompt prefix and stop paying twice for the same work |
| 6. Lever five: verified stop | Define done as a passing check, so the agent stops polishing |
| 7. Claim discipline | How to report a savings number someone else can check |
| 8. Rules block | A paragraph for CLAUDE.md, AGENTS.md or a Cursor rule |
| 9. Prompts | 10 prompts to measure, diagnose and apply the levers |
| 10. Sources | What we used and how we used it |
````

## Worth knowing

- This is a method, not a promised percentage. You measure your own savings.
- Reasoning settings, compact commands, usage reports and caching rules change often. Check current tool and provider docs for exact names.

## Questions

**How is this different from the Token saver template?** Token saver is two scripts that keep long command output out of context, which is one part of lever two and three. This pack is the whole measured routine: a baseline, five levers and a way to report the result.

**Will this make my agent worse?** Only if you keep a change that lowers the pass count. Every lever is tested against checks you write before the run, and a quality drop counts as a failed change.

## How to buy

$24 one time at https://paperchasewebb.ai/bots/marketplace/items/agent-cost-levers-cut-cost-per-solved-task/. Stripe checkout, then an instant download page; the download link is also in your emailed receipt.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com