token-saver-config skillA
token-saver-config is agent-read markdown (skill) from ppgranger/token-saver: Configure and diagnose token-saver compression settings. Use when the user asks about adjusting compression levels, checking processor status, debugging hook issues, or reviewing savings statistics..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Token-Saver Configuration & Diagnostics ## Check Status Run `token-saver stats` to see lifetime and per-command compression statistics. Add `--json` for machine-readable output. ## Check Why a Specific Command Was (or Wasn't) Compressed There is no `token-saver config` subcommand — use `explain` and `benchmark` instead: ```bash token-saver explain "git status" # routing decision: compressible? which processor? why excluded? token-saver benchmark "npm install" --dry-run # measure compression without replacing real output ``` ## Configuration Settings are read in this order (later wins): built-in defaults → `~/.token-saver/config.json` → a project-level `.token-saver.json` found by walking up from cwd → `TOKEN_SAVER_*` environment variables. There is no CLI subcommand to write these files — edit `~/.token-saver/config.json` directly, or set an environment variable. The most commonly adjusted settings and their actual defaults: - `enabled` (bool, default `true`): master on/off switch. - `min_input_length` (int, default `1`): minimum output length in characters before compression is attempted. …
Read the whole file at its exact version.
How to install
mdr add ppgranger/token-saver/token-saver-config@git:20260804.be43884mdr add ppgranger/token-saver/token-saver-config@sha256:15a1f5cccb4de37cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_chqx5loytjsfo27l)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.be43884 latest | 2026-08-04 | be43884 | 4,111 B | A | view · diff |
| git:20260307.2322767 | 2026-03-07 | 2322767 | 1,615 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4111 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ppgranger/token-saver · 153 stars · license Apache-2.0 · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_chqx5loytjsfo27l GET https://markdownregistry.com/api/v1/resolve?ref=ppgranger/token-saver/token-saver-config GET https://markdownregistry.com/api/v1/blob/15a1f5cccb4de37cf84183ccad19be57246644a0046124ab26c83262d16325f4
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.