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-designnpx skills add CNaught-Inc/claude-code-plugins --skill eco-designgit 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-design)<a href="https://agentmods.dev/skills/cnaught-inc/claude-code-plugins/eco-design"><img src="https://agentmods.dev/badge/skills/cnaught-inc/claude-code-plugins/eco-design.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.00036 | $0.02890 |
| Opus 5 | $0.00018 | $0.01445 |
| Sonnet 5 | $0.00007 | $0.00578 |
| Haiku 4.5 | $0.00004 | $0.00289 |
Grade A, and why
eco-design 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 3d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
eco-design
Walk through sustainability considerations for an architecture or feature being planned. Unlike eco-review (which audits existing code), eco-design is forward-looking — it checks whether the design being discussed has considered greener alternatives at each decision point.
Important: eco-design only evaluates the design document or plan being discussed. Do not scan or audit the existing codebase — that is eco-review's job. Only read existing code if you need to understand context for a decision the design document explicitly introduces (e.g., understanding an ORM pattern to inform a new entity's access strategy). Never surface findings about existing infrastructure, CI configuration, logging, or other concerns that are not part of the proposed design. If the design document does not mention a topic (e.g., CI/CD, container images, cloud regions), do not raise it.
Process
- Read the design document — the design doc, plan, or conversation so far. Check for
.eco-ignorein the project root; skip any decision points whose pattern ID is listed there. - Identify decision points — which items from the checklist below are relevant to decisions introduced or changed by this design
- Present recommendations — for each relevant decision point, present the eco-first alternative with its rationale and citation
- Discuss with developer — ask whether they want to adopt each recommendation; accept pushback on compliance, latency, or cost constraints
- Summarize — list accepted, declined, and deferred recommendations
Decision Points Checklist
Infrastructure Decisions
Region selection
If the design specifies a cloud region, look it up in data/carbon-intensity.md. If it's in the "High Carbon" tier, suggest a lower-carbon alternative in the same provider with comparable latency.
Technical risk: Data residency/compliance violations, migration downtime, cross-region replication complexity.
Usability risk: Higher latency for users near original region.
Reference: I1 — Google Cloud Region Carbon Data, 2024
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.
- 3d ago First seen · 210 lines · 36 tokens per session scan A fdbd6ad5c3a6
eco-design 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 36 tokens to every session and 2,890 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…