Skip to main content
Agent skill

Cli Cost Usage

View cost breakdowns, token usage, and call logs from the CLI. Filter by provider, model, or date range. Export usage reports and inspect per-connection spending.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Cli Cost Usage when an AI agent needs a reusable SKILL.md workflow for this job: View cost breakdowns, token usage, and call logs from the CLI. Filter by provider, model, or date range. Export usage reports and inspect per-connection spending.

When not to use it

Skip Cli Cost Usage when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/cli-cost-usage
# Save SKILL.md to ~/.claude/skills/cli-cost-usage/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/cli-cost-usage/SKILL.md. For a shared project, commit the folder at .claude/skills/cli-cost-usage/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Cli Cost Usage skill for this task: Use Cli Cost Usage when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

71/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

<!-- generated by src/lib/agentSkills/generator.ts; manual edits will be overwritten -->

## Overview

View cost breakdowns, token usage, and call logs from the CLI. Filter by provider, model, or date range. Export usage reports and inspect per-connection spending.

## Quick install

```bash npm install -g omniroute # or: npx omniroute omniroute --version ```

## Subcommands

### `cost`

**Flags:**

- `--period <range>` - `--since <date>` - `--until <date>` - `--group-by <field>` - `--api-key <key>` - `--limit <n>`

**Example:**

```bash omniroute cost ```

### `pricing`

**Example:**

```bash omniroute pricing ```

### `pricing sync`

**Flags:**

- `--provider <p>` - `--force`

**Example:**

```bash omniroute pricing sync ```

### `pricing list`

**Flags:**

- `--provider <p>` - `--model <m>` - `--limit <n>`

**Example:**

```bash omniroute pricing list ```

### `pricing get <model>`

**Example:**

```bash omniroute pricing get <model> ```

### `pricing defaults`

**Example:**

```bash omniroute pricing defaults ```

### `pricing show`

**Example:**

```bash omniroute pricing show ```

### `pricing set`

**Flags:**

- `--input <p>` - `--output <p>` - `--cache-read <p>` - `--cache-write <p>`

**Example:**

```bash omniroute pricing set ```

### `pricing diff`

**Flags:**

- `--model <m>`

**Example:**

```bash omniroute pricing diff ```

### `usage`

**Example:**

```bash omniroute usage ```

### `usage analytics`

**Flags:**

- `--period <range>` - `--provider <id>`

**Example:**

```bash omniroute usage analytics ```

### `usage budget`

**Example:**

```bash omniroute usage budget ```

### `usage list`

**Example:**

```bash omniroute usage list ```

### `usage get [scope]`

**Example:**

```bash omniroute usage get [scope] ```

### `usage set <amount>`

**Flags:**

- `--scope <s>` - `--period <p>`

**Example:**

```bash omniroute usage set <amount> ```

### `usage reset [scope]`

**Example:**

```bash omniroute usage reset [scope] ```

### `usage quota`

**Flags:**

- `--provider <id>` - `--check`

**Example:**

```bash omniroute usage quota ```

### `usage logs`

**Flags:**

- `--limit <n>` - `--search <q>` - `--since <ts>` - `--follow` - `--api-key <k>`

**Example:**

```bash omniroute usage logs ```

### `usage utilization`

**Flags:**

- `--api-key <k>`

**Example:**

```bash omniroute usage utilization ```

### `usage history`

**Flags:**

- `--limit <n>`

**Example:**

```bash omniroute usage history ```

### `usage proxy-logs`

**Flags:**

- `--limit <n>`

**Example:**

```bash omniroute usage proxy-logs ```

Intended uses

  • Use Cli Cost Usage when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.