carbon-budget-designer

Stars4

Forks0

UpdatedJuly 18, 2026 at 15:25

Design per-feature and per-service efficiency budgets — page-weight budgets, token budgets per AI feature, query budgets per endpoint, GPU-hour budgets per training project — with owners, review checkpoints, and enforcement hooks. Use this skill whenever the user wants sustainability targets for teams, asks how to keep efficiency from regressing organizationally, mentions performance-budget-style governance for carbon/energy, or is setting engineering standards. Part of Lean Agentic AI Skills; an advisor emitting budget definitions plus lean-findings.json.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

navveenb

navveenb/lean-agentic-ai-skills

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name

carbon-budget-designer

description

Carbon Budget Designer

Advisor skill — the organizational layer. Input: current baselines (from audit findings files where available), team/feature structure, existing review processes. Output: budget definitions + findings for anything currently unbudgeted and unowned.

Performance budgets work because they convert a value ("fast") into a number a team can defend in code review. This skill does the same for efficiency — with proxy metrics that are honestly countable, never invented carbon figures.

Subject type: emit subject.type: "organization" in findings.

Budget catalog (pick per context)

Web: page transfer budget (KB per page class), request-count budget, image-weight budget. Baseline from web-carbon-audit evidence or a Lighthouse run.
AI features: tokens per interaction budget (prompt + completion), model-tier policy (which tiers are allowed per task class — pairs with model-right-sizer), tool-calls-per-agent-task budget (pairs with agentic-loop-auditor).
APIs/services: queries per request budget (N+1 ceiling), payload-size budget, cache-hit-ratio floor.
Data: ingestion volume budget per pipeline, retention ceiling per dataset class (pairs with logging-telemetry-audit, data-minimization-designer).
ML training: GPU-hours per experiment class, sweep-trial budgets (pairs with training-efficiency-audit).
Infra: utilization floors (fleet p95 below X% triggers right-sizing review — pairs with right-size-compute).

Design rules

Budgets are proxies and say so. A KB or token budget tracks E directionally; the budget doc states the proxy relationship in one line rather than claiming carbon units it can't measure.
Baseline before target. Every budget starts from a measured current value (audit evidence, analytics, logs) — a budget with no baseline is a wish. If no baseline exists, the first "budget" is the instruction to measure for two weeks.
Every budget has an owner and a checkpoint — a named role and where it's checked (PR gate via lean-regression-gate, sprint review, quarterly). Unowned budgets decay in a quarter.
Headroom over heroics — budgets set at achievable-with-effort (typically current baseline minus the quick wins from findings), reviewed and tightened on a cadence, not set at aspirational floors that get ignored.
Exceed-with-justification path — a documented process for deliberately exceeding a budget (new feature launch) with a paydown plan, so the system bends rather than gets abandoned.

Honesty rules

No budget is denominated in gCO2 unless the org has actual measurement (via impact-framework-bridge + instrumentation) — proxy units (KB, tokens, queries, GPU-hours) are the honest default and this is a feature, not a limitation: teams can count them in CI.

Not this skill's job

Detecting violations (lean-regression-gate), producing baselines (the producer audits), measurement (impact-framework-bridge).

More from this repository

same repository

agentic-loop-auditor

navveenb/lean-agentic-ai-skills

Audit agent frameworks and agentic workflows for token-burning loop pathologies — unbounded retries, excessive planning depth, tool-call thrashing, context snowballing, missing loop budgets and kill switches. Use this skill whenever the user shares agent configs or traces (LangChain/LangGraph, CrewAI, AutoGen, custom loops), complains an agent is slow or expensive, or is designing any autonomous/multi-step agent. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

ai-eval-efficiency-audit

navveenb/lean-agentic-ai-skills

Audit AI evaluation infrastructure for wasted compute — full benchmark suites re-run on unchanged cases, LLM-as-judge grading without caching, oversized judge models, redundant eval passes per commit, and missing result reuse. Use this skill whenever the user shares eval harness configs or CI eval steps, complains that evals are slow or expensive, mentions LLM-as-judge costs, or runs benchmark suites on every change. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

api-efficiency-audit

navveenb/lean-agentic-ai-skills

Audit API design for chattiness and over-fetching — REST endpoints requiring N calls per screen, GraphQL resolvers with N+1 fan-out, default-everything payloads, missing pagination and field selection, provider-side polling where webhooks serve, and uncompressed responses. Use this skill whenever the user shares API schemas (OpenAPI, GraphQL SDL), resolver code, endpoint designs, or asks why clients make too many calls or payloads are heavy. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

caching-strategy-designer

navveenb/lean-agentic-ai-skills

Design caching layers so work is done once, not per request — HTTP/CDN caching, application-level caches (Redis/Memcached), computed-result caching, and cache-invalidation strategy. Use this skill whenever the user wants to add caching, asks why the same work is recomputed, designs a read-heavy system, or an audit skill (db-efficiency-audit, web-carbon-audit) flags uncached repeated work. Part of Lean Agentic AI Skills; emits a cache design plus lean-findings.json.

2026-07-184

carbon-aware-scheduler

navveenb/lean-agentic-ai-skills

Design time-shifting of flexible workloads (batch jobs, CI, training, backups, crons) to hours and regions when grid electricity is cleanest, using carbon-intensity signals like Electricity Maps, WattTime, or the Carbon Aware SDK. Use this skill whenever the user mentions carbon-aware computing, scheduling flexible/deferrable jobs, demand shifting, running workloads when energy is clean, or asks how to reduce the carbon intensity (not just amount) of their compute. Part of Lean Agentic AI Skills; emits schedule designs plus lean-findings.json.

2026-07-184

cloud-waste-audit

navveenb/lean-agentic-ai-skills

Find idle and orphaned cloud resources that burn money and carbon for no output — idle VMs, unattached disks/volumes, unassociated elastic IPs, zombie snapshots, forgotten load balancers, stopped-but-billed instances. Use this skill whenever the user shares cloud billing exports or resource inventories (AWS Cost Explorer/CUR, Azure Cost Management, GCP billing) and the question is about unused or forgotten resources — idle instances, waste, things running that shouldn't be — cost and carbon are two payoffs of the same fix. For costs driven by growing stored data, retention, or tiering (S3/blob bills, Storage Lens reports, "we never delete anything"), use storage-lifecycle-audit instead. Part of Lean Agentic AI Skills; emits lean-findings.json for composition with report/deck skills.

2026-07-184

name

carbon-budget-designer

description

Carbon Budget Designer

Subject type: emit subject.type: "organization" in findings.

Budget catalog (pick per context)

Web: page transfer budget (KB per page class), request-count budget, image-weight budget. Baseline from web-carbon-audit evidence or a Lighthouse run.
AI features: tokens per interaction budget (prompt + completion), model-tier policy (which tiers are allowed per task class — pairs with model-right-sizer), tool-calls-per-agent-task budget (pairs with agentic-loop-auditor).
APIs/services: queries per request budget (N+1 ceiling), payload-size budget, cache-hit-ratio floor.
Data: ingestion volume budget per pipeline, retention ceiling per dataset class (pairs with logging-telemetry-audit, data-minimization-designer).
ML training: GPU-hours per experiment class, sweep-trial budgets (pairs with training-efficiency-audit).
Infra: utilization floors (fleet p95 below X% triggers right-sizing review — pairs with right-size-compute).

Design rules

Budgets are proxies and say so. A KB or token budget tracks E directionally; the budget doc states the proxy relationship in one line rather than claiming carbon units it can't measure.
Baseline before target. Every budget starts from a measured current value (audit evidence, analytics, logs) — a budget with no baseline is a wish. If no baseline exists, the first "budget" is the instruction to measure for two weeks.
Every budget has an owner and a checkpoint — a named role and where it's checked (PR gate via lean-regression-gate, sprint review, quarterly). Unowned budgets decay in a quarter.
Headroom over heroics — budgets set at achievable-with-effort (typically current baseline minus the quick wins from findings), reviewed and tightened on a cadence, not set at aspirational floors that get ignored.
Exceed-with-justification path — a documented process for deliberately exceeding a budget (new feature launch) with a paydown plan, so the system bends rather than gets abandoned.

Honesty rules

Not this skill's job

Detecting violations (lean-regression-gate), producing baselines (the producer audits), measurement (impact-framework-bridge).