Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/cnaught-inc/claude-code-plugins/eco-reviewnpx skills add CNaught-Inc/claude-code-plugins --skill eco-reviewgit clone --depth 1 https://github.com/CNaught-Inc/claude-code-pluginsWrote 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/cnaught-inc/claude-code-plugins/eco-review)<a href="https://agentmods.dev/skills/cnaught-inc/claude-code-plugins/eco-review"><img src="https://agentmods.dev/badge/skills/cnaught-inc/claude-code-plugins/eco-review.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00048 | $0.09122 |
| Opus 5 | $0.00024 | $0.04561 |
| Sonnet 5 | $0.00010 | $0.01824 |
| Haiku 4.5 | $0.00005 | $0.00912 |
Grade A, and why
eco-review scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Tools:** `curl -sI -H 'Accept-Encoding: gzip' <url> | grep -i content-encoding` to verify compression How it starts
The opening of the file, as written. The whole thing — 573 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eco-review
Scan a project's infrastructure, code, and product design for sustainability issues. Matches findings against 27 known anti-patterns across infrastructure, code, product design, and architecture. Produces a ranked report with impact estimates, effort levels, and cited sources.
Audit Process
Step 1: Scan the Project
Search the codebase for:
- Infrastructure files: Terraform (
.tf), CloudFormation (template.yaml/.json), Pulumi, Dockerfiles, docker-compose, CI configs (.github/workflows/,.gitlab-ci.yml,Jenkinsfile) - Code patterns: API endpoints, payload handling, compression middleware, caching headers, image tags, frontend bundle configs (webpack, vite, rollup), font files (
@font-face, Google Fonts URLs), video/GIF tags, third-party script includes - Database patterns: ORM configuration (Prisma, Django ORM, ActiveRecord, TypeORM, Sequelize), query patterns, logging configuration
- Product design: Default settings, notification systems, content loading patterns, data retention configs, background feature toggles
- Suppression file: Check for
.eco-ignorein the project root. Each line contains a pattern ID (e.g.,I7,C8) with optional comment after#. Skip suppressed patterns in Steps 2-4. List them at the end of the report.
Step 2: Match Against Patterns
Compare findings against each pattern in the pattern set below. Record every match with the specific file and line where the anti-pattern appears.
Step 3: Look Up Cloud Regions
If cloud region configuration is found, look up the region in the carbon intensity reference in data/carbon-intensity.md. Note the grid carbon intensity and identify lower-carbon alternatives in the same provider.
Step 4: Produce the Report
Generate the output report using the format specified below.
Output Format
## Eco-Review: [Project Name]
> **[Cø] Powered by CNaught** — carbon-aware code intelligence
### TL;DR
1. [problem] — [fix] ([effort])
2. [problem] — [fix] ([effort])
3. [problem] — [fix] ([effort])
### Category Summary
#### Infrastructure
- ✓ [Good practice found]
1. **[Pattern ID]:** [Recommendation] ([effort])
2. ...
#### Code
- ✓ [Good practice found]
1. **[Pattern ID]:** [Recommendation] ([effort])
2. ...
#### Product Design
- ✓ [Good practice found]
1. **[Pattern ID]:** [Recommendation] ([effort])
2. ...
#### Architecture
- ✓ [Good practice found]
1. **[Pattern ID]:** [Recommendation] ([effort])
2. ...
Numbers restart at 1 within each category. Include the pattern ID and effort label on each numbered item. This introduces the pattern ID prefixes (I = Infrastructure, C = Code, P = Product Design, A = Architecture) in context.
### Sustainability-Specific Findings
These are issues you would only identify through a sustainability lens.
**[Pattern ID]: [Description]**
Found in: `[file:line]`
Impact: [contextualized to this project — never copy verbatim from pattern definition]
Sustainability impact: [Explain specifically how fixing this reduces energy, compute, storage, or emissions — e.g., "switching from us-east-1 to us-west-2 would reduce grid carbon intensity from 323 to 79 gCO2/kWh" or "eliminating idle compute for 80% of off-peak hours"]
Effort: [Quick win / Next sprint / Roadmap] · Risk: [Low / Medium / High]
[For Roadmap items, add a one-line empathy note: "This may not be practical because [reason] — consider for future planning."]
Source: [citation from pattern]
### Engineering Co-Benefits
Standard best practices that also reduce environmental impact.
**[Pattern ID]: [Description]**
Found in: `[file:line]`
Impact: [contextualized to this project — never copy verbatim from pattern definition]
Effort: [Quick win / Next sprint / Roadmap] · Risk: [Low / Medium / High]
Source: [citation from pattern]
### Worth Checking
[Bulleted list of patterns the audit could not verify from the codebase but suspects may apply. Keep brief — one line per item with the pattern ID and what to check. Omit this section if everything was verified.]
### Suppressed Patterns
[Pattern IDs from .eco-ignore, if any. Omit this section if no .eco-ignore exists.]
---
*Generated by [CNaught Carbonlog](https://github.com/CNaught-Inc/claude-code-plugins/tree/main/plugins/carbonlog)*
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.
- 5d ago First seen · 573 lines · 48 tokens per session scan A 094f14692ac6
eco-review is a skill published in the GitHub repository CNaught-Inc/claude-code-plugins (5 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 9,122 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…