/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
Claude Code
$ npx -y skills add Green-PT/honey-for-devs --skill honey-eco --agent claude-code
Codex
$ npx skills add Green-PT/honey-for-devs --skill honey-eco -a codex -y
Cursor
$ npx skills add Green-PT/honey-for-devs --skill honey-eco -a cursor -y
Gemini CLI
$ npx skills add Green-PT/honey-for-devs --skill honey-eco -a gemini-cli -y
GitHub Copilot
$ npx skills add Green-PT/honey-for-devs --skill honey-eco -a github-copilot -y
OpenCode
$ npx skills add Green-PT/honey-for-devs --skill honey-eco -a opencode -y
Windsurf
$ npx skills add Green-PT/honey-for-devs --skill honey-eco -a windsurf -y
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 the output tokens AI coding agents spend — making them emit less code and less prose without losing correctness.
Other skills on honey.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about honey-eco.
- Which coding agents can use honey-eco?
- honey-eco installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

