Xerg

Xerg is a local-first CLI for finding wasted AI runtime spend. Runtime audits separate three evidence-strict monetary findings from seven neutral signals, report detector coverage, and use --compare to measure compatible changes. Runtime costs may be observed, locally estimated, or unpriced; they are not authoritative provider invoices.

Hosted pricing uses Monthly Audited Agent Spend from known spend in explicitly pushed runtime audits: Free through $2,000 per UTC month, Team at $99 through $10,000, Growth at $299 through $50,000, Scale at $799 through $250,000, and custom Enterprise above $250,000. Team, Growth, and Scale have identical capabilities. Historical imports, duplicate-review spend, and unpriced usage do not count toward MAAS.

Cold-fetch setup

When this file was fetched from https://xerg.ai/skill.md (including via the link on the npm listing for @xerg/cli) rather than loaded from an installed skill:

Identify the current agent host. OpenClaw, Hermes, QM, Claude Code, Cursor, and Codex are setup hosts; they are not automatically the data source being audited. QM can also be the audit source, but only through its explicit administrator-provisioned Xerg connection.
Check whether Xerg is already installed for this host. Before writing to a persistent or global skill directory, explain the destination and ask the user for permission.
If the host has a supported skill installer, use it after permission. OpenClaw can install xerg from ClawHub. Agent Skills hosts can install the public xergai/skills repository. Hermes can use Xerg's well-known skill discovery. Deterministic host-specific commands live at xerg.ai/agents.
If persistent installation is unavailable or declined, use these fetched instructions for the current session. Do not invent an install location.
Ask permission before any npm download or install, including the transient package fetch that npx may perform. Separately ask permission before reading/analyzing local runtime data. After both applicable approvals, run npx --yes @xerg/cli@latest doctor --json, parse its canAudit and recommendedCommand, and offer to execute that exact recommendation. On QM, do not use bare doctor: follow the private-scope QM procedure below.

Always ask before uploading. A local audit needs no account and must not be pushed automatically. On an approved hosted command only, set XERG_SETUP_METHOD=skill and set XERG_AGENT_HOST to the current execution host: claude_code, cursor, hermes, codex, openclaw, qm, or other. These are best-effort, content-free analytics metadata, not authentication or the audit source. If the user's setup prompt includes an Xerg organization ID, preserve it with --organization-id on activation. After a successful local result, offer to connect and push it with both markers on that same command, for example from Codex: