Home / ppgranger / token-saver · GitHub

token-saver-config SKILL.md skillA

token-saver-config from ppgranger/token-saver is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add ppgranger/token-saver/token-saver-config@git:20260804.be43884

Pins git:20260804.be43884 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: ppgranger/token-saver
Path: skills/token-saver-config/SKILL.md
Versions recorded: 2
Latest version: git:20260804.be43884, committed Aug 4, 2026
First version recorded: Mar 7, 2026
Size: 4,111 bytes
Repository stars: 162
License: Apache-2.0

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file 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

The exact contents, by fingerprint

mdr add ppgranger/token-saver/token-saver-config@sha256:15a1f5cccb4de37c

The line at the top of this page pins the label git:20260804.be43884, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_chqx5loytjsfo27l.svg)](https://markdownregistry.com/a/art_chqx5loytjsfo27l)

4 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Mar 7, 2026 and Aug 4, 2026, about one every 150 days.

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

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

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

GitHub

ppgranger/token-saver · 162 stars · license Apache-2.0 · pushed 2026-11-05 · 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 AI assistant 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.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.