Honey PX
An image's token cost is fixed by its pixel area, not its character count.
Dense text packs ~3 chars per image-token vs ~1 as text, so a 90k-char file
read as PNG pages costs a fraction of the text read. pxpipe export
(teamchong/pxpipe) does the rendering; the agent Reads the pages.
Lossy by design — misreads of exact strings are silent confabulations,
not errors. The export writes a factsheet.txt carrying the verbatim
precision tokens (paths, SHAs, ids, numbers) as text alongside the images;
always read it too.
When to use
- Bulk is read-only reference: skimming a big vendored file, a large diff
for review context, docs, generated code — content you reason over, not
byte-copy.
- Dense (code, JSON, logs) and big — worth it above ~6k chars; the
export prints
% saved, skip if it's low. Sparse prose loses money.
- The reader is Fable-class. Opus misreads ~7% of renders; other models
degrade — read as text there.
Don't use
- Files you will Edit —
old_string must be byte-exact; imaged reads
aren't. Read the real file (with offset/limit) before any edit.
- Secrets, hashes, ids, numeric values you'll act on — treat anything
exact recalled from an image as unverified; re-
Grep the source first.
- Anything the user asked to see verbatim, or that gets written back.
- Small or sparse content — the fixed pixel cost loses.
How
npx pxpipe-proxy export --json --out <scratchpad> <file-or-dir> # or --git / --diff <ref> / --stdin
Output dir pxpipe-export-<hash>/ contains page-*.png, factsheet.txt,
manifest.json (token report). Then:
Read every page-*.png and factsheet.txt. If instead you pass the
renders to a model over the raw API (subagent prompt, panel), include the
export's prompt.txt banner — naked dense renders can trip
stop_reason: refusal on Fable-class models; the banner prevents it.
- Treat the manifest's
percentSaved as the go/no-go — if it printed low,
read the text instead.
- Before acting on any exact string seen only in an image, verify it against
the source with
Grep.
Cheaper still is not reading at all — Grep/offset/limit (Lever 3b) and
eson crush (CCR) come first. PX is for when you genuinely need the whole
bulk in view.
1---2name: honey-px-43description: "Read huge dense read-only text as PNG pages via pxpipe export: ~60-75% fewer input tokens. Lossy on exact strings; never for files you will edit."4homepage: https://github.com/Green-PT/honey-for-devs5license: MIT6metadata:7 source: https://skillmd.com/skills/green-pt/honey-px-48---910# Honey PX1112An image's token cost is fixed by its pixel area, not its character count.13Dense text packs ~3 chars per image-token vs ~1 as text, so a 90k-char file14read as PNG pages costs a fraction of the text read. `pxpipe export`15(teamchong/pxpipe) does the rendering; the agent `Read`s the pages.1617**Lossy by design** — misreads of exact strings are *silent confabulations*,18not errors. The export writes a `factsheet.txt` carrying the verbatim19precision tokens (paths, SHAs, ids, numbers) as text alongside the images;20always read it too.2122## When to use2324- Bulk is **read-only reference**: skimming a big vendored file, a large diff25 for review context, docs, generated code — content you reason over, not26 byte-copy.27- **Dense** (code, JSON, logs) and **big** — worth it above ~6k chars; the28 export prints `% saved`, skip if it's low. Sparse prose loses money.29- The reader is **Fable-class**. Opus misreads ~7% of renders; other models30 degrade — read as text there.3132## Don't use3334- Files you will **Edit** — `old_string` must be byte-exact; imaged reads35 aren't. Read the real file (with `offset`/`limit`) before any edit.36- **Secrets, hashes, ids, numeric values you'll act on** — treat anything37 exact recalled from an image as unverified; re-`Grep` the source first.38- Anything the user asked to see verbatim, or that gets written back.39- Small or sparse content — the fixed pixel cost loses.4041## How4243```sh44npx pxpipe-proxy export --json --out <scratchpad> <file-or-dir> # or --git / --diff <ref> / --stdin45```4647Output dir `pxpipe-export-<hash>/` contains `page-*.png`, `factsheet.txt`,48`manifest.json` (token report). Then:49501. `Read` every `page-*.png` **and** `factsheet.txt`. If instead you pass the51 renders to a model over the raw API (subagent prompt, panel), include the52 export's `prompt.txt` banner — naked dense renders can trip53 `stop_reason: refusal` on Fable-class models; the banner prevents it.542. Treat the manifest's `percentSaved` as the go/no-go — if it printed low,55 read the text instead.563. Before acting on any exact string seen only in an image, verify it against57 the source with `Grep`.5859Cheaper still is not reading at all — `Grep`/`offset`/`limit` (Lever 3b) and60`eson crush` (CCR) come first. PX is for when you genuinely need the whole61bulk in view.