cxm-agent-plugin

Plugin cxm-agent-plugin from marketplace cxm-marketplace in cxmlabs/cxm-plugin. Commands read from the repo's manifest — yesterday.

Skills (16)

• cxm-architecture-review

  Use when the user asks to review their architecture or a proposed change, wants their design questioned for cost, asks "is this the right/cheapest way", or is adding significant cloud infrastructure. Also when the user asks for a diagram of a proposed design or change. Composes CloudExMachina's cost

• cxm-cloud-context

  Use WHENEVER the user asks about their own cloud in an understanding sense — what a resource/service/account/app is, what it is for, why it exists, how it's set up, who owns it, how things connect, naming, tags and tagging, cost allocation, untagged or unallocated spend, environments, standards/conv

• cxm-cloud-topology

  Use when the user asks about their cloud footprint, account structure, which clouds/accounts/regions they use, multi-cloud posture, or where their spend is concentrated across accounts, or asks to draw, map or diagram their accounts, regions, organization or what is deployed where. Describes the con

• cxm-commitments

  Use when the user asks whether to buy, or how much to buy, of Savings Plans or Reserved Instances — "should we buy more commitment", "how much SP should I add", "size an RI purchase", "what commitment should we lock in". Sizes a layered buy list from the commitment ladder and the Reservation fleet,

• cxm-cost-drivers

  Use when the user asks about their cloud costs, cloud bill, top spend, biggest cost drivers, or where their cloud money goes, or asks to chart, graph or plot their spend or its trend. Use it before raw `aws ce` calls. Queries the top spend-by-service for their connected CloudExMachina organization.

• cxm-cost-of-change

  Use when the user is writing or reviewing Terraform / IaC, running AWS CLI to create resources, or asking "what will this cost". Estimates the monthly cost of a cloud resource change from CloudExMachina's rate catalog before it is applied.

• cxm-create-ticket

  Use when the user wants to turn a cost-saving finding or a CloudExMachina opportunity into an actionable ticket in their own tracker (GitHub Issues, Jira, Linear). Writes an owner-ready ticket with scope, savings, steps, evidence, and rollback.

• cxm-hunt

  Use when the user wants to actively hunt for NEW cost-saving opportunities on their cloud that CloudExMachina hasn't already flagged — "find me savings", "dig for waste", "what am I overspending on that isn't in CXM yet". Runs a guided waste hunt using the user's own cloud access plus CXM data.

• cxm-opportunities

  Use when the user asks about savings, cost optimization, savings opportunities, waste, rightsizing, or how to reduce their cloud bill, or asks for a chart of their savings. Queries current AI-discovered optimization opportunities for their connected CloudExMachina organization.

• cxm-opportunity-lifecycle

  Use when the user wants to review the status of their tracked CloudExMachina opportunities, mark ones as in-progress or done, or sweep the backlog to see what's still valid. Re-checks tracked opportunities against the live cloud and moves their status.

• cxm-repo-graph

  Use when working IN a code or infrastructure repo and you want to connect what you're reading or editing to the live cloud — a Terraform resource's real ARN, its cost, its owner, its opportunities, and what depends on it — including links into OTHER repos you don't have checked out. Backed by CloudE

• cxm-report-opportunity

  Use when the user has found a cost-saving opportunity (idle/oversized/misconfigured resource) and wants to save it into CloudExMachina to track it, or asks to "report this to CXM", "log this finding", "create an opportunity". Writes a tracked opportunity into the CXM app.

• cxm-service-limits

  Use when the user asks about an AWS service limit, quota, or maximum — "max IOPS on gp3", "how many X can I have", "what's the limit/quota/ceiling for Y", or any capacity ceiling that gates a rightsizing or scaling plan. Limits change over time; verify, never recall.

• cxm-waste

  Use when the user asks about waste, anti-patterns, flagged issues, suspicious resources, "what looks wrong", OR asks for a chart of waste, OR asks to clean up / tidy / reduce waste in an environment or account (e.g. "clean up the dev environment"). Lists CloudExMachina's detected smells for the conn

• cxm-whoami

  Use when the user wants to check their CloudExMachina connection, verify they are logged in, confirm which organization is active, or test that the CXM plugin works.

• cxm-workload-context

  Use when the user asks about their workload makeup — prod vs dev/staging split, stateful vs stateless, customer-facing vs internal, ownership, criticality, or compliance frameworks — for their connected CloudExMachina organization.

Slash commands (1)

• /cxm-agent-plugin:cxm

  Run a CloudExMachina plugin command (auth, price, savings, commitments, context, analytics)

Hooks (5)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}/scripts/install-cxm-shim.sh"

• SessionStart

  node "${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}/bin/cxm.js" hook session-start

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}/bin/cxm.js" hook iac-cost

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}/bin/cxm.js" hook aws-cost

• SessionEnd

  node "${CLAUDE_PLUGIN_ROOT:-$PLUGIN_ROOT}/bin/cxm.js" hook session-end

Similar plugins