Honey Ccr

Honey CCR

The cheapest token is the one not sent. A 500-row log read for one error line costs 500 rows of context. CCR keeps the rows that carry signal and caches the rest — recoverable by hash, so nothing is lost.

Borrowed from headroom's SmartCrusher. Lossy by design — only for data you skim, never for payloads where every row matters (e.g. a code-review handoff where the implementer needs all findings; use eso encode losslessly there).

When to use

• A tool returns a uniform JSON array of many records (≥ ~5 items, redundant).
• You need to read it but mostly skim — logs, search hits, metrics, events.
• The full data stays reachable, so dropping the boring middle is safe.

Don't use

• Small arrays (passes through untouched anyway) or non-array data.
• Any array where every element is load-bearing — encode it, don't crush it.

How

tool-that-spews-json | eso crush          # → sampled view + sentinel; originals cached
eso retrieve                         # → the full original array, verbatim

crush prints the kept sample plus a sentinel {"_ccr":">"}. When you need a dropped row, read the hash from the sentinel and run eso retrieve .

• Cache dir: .honey-ccr/ (override with HONEY_CCR_DIR).
• Below the size gate, crush returns the array unchanged with no sentinel — safe to pipe anything.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Green-PT
• Source: Green-PT/honey-for-devs
• License: MIT
• Homepage: https://github.com/Green-PT/honey-for-devs

Install and usage instructions live in the source repository linked above.