/honey-eco
Report this session's output tokens and CO₂ by running the repo's committed EcoLogits port, plus the modelled CO₂/$ saved vs a no-Honey baseline — always labelled with the bench stamp it came from. Use when asked how much Honey saved, the session's carbon/token footprint, or to
$ npx -y skills add Green-PT/honey-for-devs --skill honey-eco --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/honey-eco
Context preview
The summary Claude sees to decide when to auto-load this skill.
Report this session's output tokens and CO₂ by running the repo's committed EcoLogits port, plus the modelled CO₂/$ saved vs a no-Honey baseline — always labelled with the bench stamp it came from. Use when asked how much Honey saved, the session's carbon/token footprint, or to
SKILL.md
honey-eco.SKILL.mdname: honey-eco
description: >-
Report this session's output tokens and CO₂ by running the repo's committed
EcoLogits port, plus the modelled CO₂/$ saved vs a no-Honey baseline — always
labelled with the bench stamp it came from. Use when asked how much Honey saved,
the session's carbon/token footprint, or to expand the 🍯 statusline badge into a
full breakdown.
license: MIT
Honey Eco
Surface the numbers the carbon badge is based on. **Never estimate by hand** — run the committed report so the figure matches `hooks/eco.js` (the verified EcoLogits v0.8.2 port) exactly.
Do
Run, from the repo root — zero-dependency, reuses the same `hooks/eco.js` the badge uses:
node scripts/eco-session.js # newest session
node scripts/eco-session.js --transcript PATH --mode full
Then report terse — output tokens, CO₂eq (g), and the `saved` line — in a line or two. Keep the exact numbers the script prints; don't round away precision.
Two numbers, two epistemic statuses — never merge them
- **CO₂eq is measured** for this session: real output tokens through the EcoLogits port.
- **`saved` is not.** It is a *modelled counterfactual* — how many tokens a no-Honey run
would have emitted — taken from a committed bench stamp. Always pass through the `basis:` line the script prints (stamp, model, n, p). Never state a savings figure without it, and never re-derive one by hand.
When the script prints `saved : —`, no committed stamp covers this session's model. Say that. Do not extrapolate from another model's ratio — that is exactly how a tool ends up reporting savings while the invoice goes up.
For the authoritative breakdown (usage + embodied + primary energy) the user can run the Python path, which needs the real package:
pip install ecologits && python scripts/eco_report.py
Say once, don't bury
The params are **speculative** (Anthropic discloses none). The badge shows **served** impact — EcoLogits' single-stream (batch-1) ceiling divided by `serving_concurrency` (continuous-batching amortization); `eco-session.js`/`eco_report.py` also print the raw ceiling. State that once, briefly, then give the number. The badge renders only in Claude Code (its transcript is all Claude models).
Boundaries
Report only — don't change config or mode (that's the `/honey` command). The number is a range, not a meter reading; present it as one.
Read more
name: honey-eco description: >- Report this session's output tokens and CO₂ by running the repo's committed EcoLogits port, plus the modelled CO₂/$ saved vs a no-Honey baseline — always labelled with the bench stamp it came from. Use when asked how much Honey saved, the session's carbon/token footprint, or to expand the 🍯 statusline badge into a full breakdown. license: MIT
Honey Eco
Surface the numbers the carbon badge is based on. **Never estimate by hand** — run the committed report so the figure matches `hooks/eco.js` (the verified EcoLogits v0.8.2 port) exactly.
Do
Run, from the repo root — zero-dependency, reuses the same `hooks/eco.js` the badge uses:
node scripts/eco-session.js # newest session node scripts/eco-session.js --transcript PATH --mode full
Then report terse — output tokens, CO₂eq (g), and the `saved` line — in a line or two. Keep the exact numbers the script prints; don't round away precision.
Two numbers, two epistemic statuses — never merge them
- **CO₂eq is measured** for this session: real output tokens through the EcoLogits port.
- **`saved` is not.** It is a *modelled counterfactual* — how many tokens a no-Honey run
would have emitted — taken from a committed bench stamp. Always pass through the `basis:` line the script prints (stamp, model, n, p). Never state a savings figure without it, and never re-derive one by hand.
When the script prints `saved : —`, no committed stamp covers this session's model. Say that. Do not extrapolate from another model's ratio — that is exactly how a tool ends up reporting savings while the invoice goes up.
For the authoritative breakdown (usage + embodied + primary energy) the user can run the Python path, which needs the real package:
pip install ecologits && python scripts/eco_report.py
Say once, don't bury
The params are **speculative** (Anthropic discloses none). The badge shows **served** impact — EcoLogits' single-stream (batch-1) ceiling divided by `serving_concurrency` (continuous-batching amortization); `eco-session.js`/`eco_report.py` also print the raw ceiling. State that once, briefly, then give the number. The badge renders only in Claude Code (its transcript is all Claude models).
Boundaries
Report only — don't change config or mode (that's the `/honey` command). The number is a range, not a meter reading; present it as one.
Write less code and say less about it. Honey (I Shrunk the AI) by GreenPT is a cross-tool coding skill that cuts AI coding-agent token usage and LLM API costs — making agents emit less code and less prose without losing correctness.
Repo: Green-PT/honey-for-devs
Other skills on honey.
- /honey-ccr
Compress-Cache-Retrieve for huge, repetitive array tool output (logs, scan results, time series, event streams) before it enters context. Keeps an informative sample — endpoints, anomalies/change-points, head/tail — drops the redundant rest to a local cache, and leaves a
Open skill - /honey-chat
Honey for plain Claude — the terse-prose core with no agent-harness features. Paste into a claude.ai Project's custom instructions, a Style, or an API system prompt. Strips filler, hedging, and pleasantries from every response while keeping facts, names, numbers, steps, and code
Open skill - /honey-compress
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
Open skill - /honey-debt
Harvest every `honey:` comment in the codebase into a debt ledger, so the deliberate shortcuts Lever 1 leaves behind get tracked instead of rotting into "later means never". Flags markers with no revisit trigger — those are the ones that go permanent silently. Use when the user
Open skill - /honey-design
Same pixels, fewer tokens — for user-facing deliverables where visual polish is the spec. Use when building or editing a landing page, marketing site, hero, pricing/feature section, dashboard, or any HTML/CSS UI component. Keeps the full rendered design (layout depth, hierarchy,
Open skill - /honey-gain
Show Honey's benchmark scoreboard — the committed quality and token results per task tier (code, user-facing, agent-to-agent) from bench/. Reports only the reproducible committed figures, never invents per-repo numbers. Use when asked how much Honey saves, how it compares to
Open skill