cloudzero-claude-marketplace

Use when proactively scanning for cost anomalies, unusual spending, unexpected charges, or irregular patterns — during weekly reviews, after incidents, or when something looks off

Use when comparing costs between time periods, environments, accounts, regions, or teams to understand spending differences and identify inefficiencies

Project the monthly cost of an infrastructure definition (Terraform, CDK, CloudFormation, SAM) using CloudZero spend data. Reads IaC files, enumerates resources, and produces a line-item cost breakdown.

Use when a cost spike or unexpected increase has already been identified and you need to find which service, account, or resource is responsible

Use when analyzing whether costs are growing, declining, or stable over time — for forecasting, budget planning, or understanding spending velocity

Use when analyzing costs by organization-specific dimensions like teams, products, business units, or applications for showback, chargeback, or business-aligned cost reporting

Analyze code diffs for infrastructure cost impact using CloudZero spend data. Detects Terraform, CDK, CloudFormation, SAM, K8s, scaling, and application code changes that affect cloud spending.

One-shot, PER-CALL-SITE audit of a repo's EXISTING LLM calls — every place code invokes a model (an SDK/API call, a sub-agent dispatch, an agent frontmatter definition), decomposed by INTENT into the distinct jobs it does, never a grep hit on a model name and never one candidate per file. A skill pinned by one static `model:` key still gets its steps split by intent when severable under Claude Code's per-turn model binding. DELEGATES each call to `model-right-sizer-dryrun` (never re-implements its scoring) and merges results into ONE schema-conformant JSON blueprint committed at the TARGET REPO'S ROOT via a PR — never a markdown table. Distinct from `model-right-sizer-dryrun` (invoke directly for one hypothetical task) and `model-right-sizer-install` (the standing before/after mandate). Use when someone says "audit this repo's model calls", "right-size the models in <repo> per call site", "find every LLM call and right-size it", or "commit a model right-sizing blueprint for <repo>".

Preview the model-routing MAP for an intent without building anything. You give it a free-text INTENT — "build a CLI that…", "add a feature that…", "refactor X into Y" — and it invokes the `model-right-sizer` agent in BLUEPRINT-ONLY mode: decompose the work, score each piece, and emit a single schema-conformant JSON blueprint (task→model→effort→budget→ schema→confidence, per `schemas/blueprint.schema.json`), then STOP. No build, no file edits, no after-the-fact usage report — it is the what-would-this-cost / how-would-this-route preview lever, safe to run against any idea, and the JSON it returns is what an orchestrator parses to route dispatch. Read-only. Use when someone says "dry-run the right-sizer on …", "what's the map for …", "how would you route …", or "show me the blueprint for … before I build it".

Stamp a model-right-sizer mandate onto the CURRENT repo's agent-instructions file — `CLAUDE.md`, `AGENTS.md`, or both, whichever the repo has. Idempotent and append-only: an existing file is never overwritten, only the marker-delimited mandate block is inserted or refreshed. The mandate's "before" hook runs `model-right-sizer-dryrun` to produce a schema-conformant JSON blueprint for the orchestrator to route by. Also checks whether the `model-right-sizer` agent and `model-right-sizer-dryrun` skill are discoverable and, if either is missing, installs the `model-right-sizer` Claude Code plugin to fix that (falling back to manual instructions otherwise). Deliberately narrow and organization-agnostic — installs only the right-sizing mandate (plus its own dependencies, if absent), not any broader development process. Use when someone says "install model-right-sizer in this repo", "init this repo for model-right-sizer", "add the right-sizer mandate here", or "make this repo consult model-right-sizer every turn".

Prescribe a minimal output schema for ONE agent's handoff to its controller — the `model-right-sizer` agent's "Agent-to-agent message-schema design" lever, scoped to a single seam instead of a whole flow's blueprint. Given a target agent (a path to an existing agent `.md` file, or a description of one not yet written), returns a schema-conformant JSON prescription (`schemas/agent-schema.schema.json`) naming the reusable family the agent's reply fits, typed `in`/`out` fields, an exclusion list, and a ready-to-insert `## Agent-to-agent schema` markdown stamp — reproduced here in portable, organization-agnostic form. Offers to stamp that block directly into the target agent's file, idempotently. The point: an agent that used to hand its controller unscoped prose now hands it typed fields plus one bounded prose slot. Use when someone says "give this agent an output schema", "prescribe a schema for …", "minimize what this agent returns", or "stamp an agent-to-agent contract on …".

Fetch top unaddressed CloudZero Optimize recommendations, dispatch parallel research agents per item, apply SRE critique, and surface actionable findings with confidence verdicts and per-resource report files. Read-only research only.

Cut a release of this repository (the CloudZero plugin marketplace itself — not a customer-facing plugin). Promotes every touched plugin's own `Unreleased` changelog section to a dated entry, synthesizes those changes into a new SemVer section at the top of the root `CHANGELOG.md`, bumps `.claude-plugin/marketplace.json`'s version, runs the full CI validation suite locally, tags the release, publishes a GitHub Release, and opens the companion docs PR against `Cloudzero/cloudzero-documentation`'s `v2.0` branch so customer-facing docs land in step with the code. This is a maintainer-only, repo-local skill (lives in `.claude/skills/`, not inside a `plugins/*/skills/` directory) — it is never installed by marketplace consumers. Use when told "cut a release", "release the marketplace", "ship a new version", "promote the changelog", or after merging PR(s) that need a version bump and a docs update — mirroring how v1.2.0 (the Model Right Sizer launch) shipped.

Use when you need a detailed breakdown of a specific cloud service's costs — EC2, RDS, S3, Lambda, etc. — to understand usage patterns and find optimization opportunities

Use when evaluating how well cloud resources are tagged for cost allocation — to find untagged costs, improve showback accuracy, or prepare for chargeback reporting

Use when identifying where cloud spend is concentrated — which services, accounts, teams, or regions are driving the most cost — to prioritize optimization efforts

Use at the start of any CloudZero cost analysis session to load organization-specific context — custom dimensions, team structures, cost allocation policies, and workflows