Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Green-PT/honey-for-devsnpx agentmods add skills/green-pt/honey-for-devs/honey-ecoWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/green-pt/honey-for-devs/honey-eco)<a href="https://agentmods.dev/skills/green-pt/honey-for-devs/honey-eco"><img src="https://agentmods.dev/badge/skills/green-pt/honey-for-devs/honey-eco/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/green-pt/honey-for-devs/honey-eco"><img src="https://agentmods.dev/badge/skills/green-pt/honey-for-devs/honey-eco.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00018 | $0.00554 |
| Opus 5 | $0.00009 | $0.00277 |
| Sonnet 5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
honey-eco scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
savedis 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 thebasis: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.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 52 lines · 18 tokens per session scan A a709266f1ea4
honey-eco is a skill published in the GitHub repository Green-PT/honey-for-devs (294 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 554 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.