Skip to content
Back to skills

Honey Compress

ASecurity

Rewrite a memory or context file (CLAUDE.md, AGENTS.md, a todo or notes file) into Honey-terse form so it costs fewer input tokens every session, without losing meaning. Backs up the original first. Use when asked to shrink or compress context files, trim CLAUDE.md, or cut per-session input cost. Prose only — never code, config, or data.

  • 306 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 3, 2026
ai-agents

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add Green-PT/honey-for-devs --skill honey-compress --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Honey Compress?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Honey Compress
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/green-pt-honey-compress-8eae0d5b/badge)](https://www.skillsdirectory.com/skills/green-pt-honey-compress-8eae0d5b)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: honey-compress
description: >-
  Rewrite a memory or context file (CLAUDE.md, AGENTS.md, a todo or notes file)
  into Honey-terse form so it costs fewer input tokens every session, without
  losing meaning. Backs up the original first. Use when asked to shrink or
  compress context files, trim CLAUDE.md, or cut per-session input cost. Prose
  only — never code, config, or data.
license: MIT
---

# Honey Compress

Apply Lever 2 to a file the agent re-reads every session. The cheapest token is the one not re-sent — a one-time rewrite that saves on every future load.

## Do

1. **Back up first.** Copy `FILE` → `FILE.original.md`. If that backup already exists, stop and ask — never clobber a restore point. If no backup can be written, refuse.
2. **Rewrite the prose tersely** — drop wind-up, hedging, narration, and redundancy; fragments over paragraphs; merge guidance that repeats.
3. **Preserve every distinct instruction** — terser words, identical rules. If unsure whether a line changes behavior, keep it verbatim.
4. **Report** original vs new line/byte count and the backup path.

## Keep exact — never compress

- Code blocks, commands, paths, identifiers, versions.
- Any **load-bearing directive** — MUST/NEVER rules, and anything touching auth, secrets, money, migrations, or deletes. Compressing an instruction that changes behavior moves cost, it doesn't remove it.

## Don't

- Don't touch code, config, or data files — prose context only.
- Don't merge two rules into one if they differ in effect.
- Don't compress a file you can't back up.

## Boundaries

Reversible by design — `FILE.original.md` is the restore path. Verify the rewrite still carries every rule before reporting done.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.