← Back to Skills Marketplace
Openrouter Usage
by
Luis Cajigas
· GitHub ↗
· v0.1.0
421
Downloads
2
Stars
3
Active Installs
1
Versions
Install in OpenClaw
/install openrouter-usage-info
Description
Track OpenRouter API spending — credit balance, per-model cost breakdown, and spending projections from OpenClaw session logs.
Usage Guidance
This package appears internally consistent with its purpose, but before installing: 1) verify the package source (the registry lists source/homepage as unknown; prefer installing from a trusted GitHub repo or reviewing the code you downloaded), 2) review install.sh to confirm you are comfortable with a CLI being placed in ~/.local/bin and an optional symlink into ~/.openclaw/workspace/skills, 3) understand the tool will read your OpenClaw session logs (~/.openclaw/agents/*/sessions/*.jsonl) and any OpenClaw auth files (~/.openclaw/agents/*/agent/auth.json) to auto-discover keys, and it will send your OpenRouter API key to openrouter.ai when fetching credits — if you are uneasy, create or use a limited/revocable API key, or run the script in a sandbox and inspect its output first.
Capability Analysis
Type: OpenClaw Skill
Name: openrouter-usage-info
Version: 0.1.0
The OpenClaw skill bundle 'openrouter-usage' is a benign utility designed to track OpenRouter API spending. It legitimately accesses the OpenRouter API (openrouter.ai) to fetch credit balance and reads local OpenClaw session logs (`~/.openclaw/agents/*/sessions/*.jsonl`) to provide per-model cost breakdowns. The `install.sh` script performs standard user-level installation, creating a CLI wrapper and an optional symlink for the skill, without any malicious commands or unauthorized system modifications. The `SKILL.md` and `README.md` provide clear, non-malicious instructions and documentation, with no evidence of prompt injection attempts or hidden agendas.
Capability Assessment
Purpose & Capability
The skill claims to report OpenRouter credits and per-model usage from OpenClaw session logs and the code does exactly that: it queries openrouter.ai for credit info and parses ~/.openclaw/agents/*/sessions/*.jsonl for per-model cost. The only required binary is the CLI wrapper it installs (openrouter-usage), which is consistent with the README/SKILL.md.
Instruction Scope
SKILL.md instructs running the provided CLI and documents that the API key is auto-discovered and that session parsing is local (reads ~/.openclaw/agents/*/sessions/*.jsonl). The Python script also only reads those local files and calls the OpenRouter API; it does not reference other system paths or external endpoints beyond openrouter.ai.
Install Mechanism
There is no remote installer: install.sh writes a wrapper to ~/.local/bin and can optionally symlink the skill into ~/.openclaw/workspace/skills — this is a local install and expected. Note: the registry metadata called this an instruction-only skill, but code files and an installer are present in the package (minor inconsistency). Also README suggests cloning a GitHub repo as the install source, but the registry entry lists source/homepage as unknown; verify the repository origin before running the installer.
Credentials
No required environment variables are declared, which matches registry metadata; however the script will optionally use OPENROUTER_API_KEY (env) or keys found in ~/.openclaw/agents/*/agent/auth.json. This is proportionate for its purpose (it needs an OpenRouter key to query credits) but you should be aware the key will be sent to openrouter.ai in an Authorization header.
Persistence & Privilege
The skill does not request always:true. The installer may create a CLI in ~/.local/bin and optionally link the skill into the user's OpenClaw workspace (with explicit prompt). It does not modify other skills or global system config beyond those user-visible local changes.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openrouter-usage-info - After installation, invoke the skill by name or use
/openrouter-usage-info - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release — track OpenRouter API spending from your OpenClaw agent.
- View credit balance, model-by-model cost breakdown, and spending projections.
- Flexible reporting: full report, credits only, or detailed per-model breakdown.
- Filter by timeframe (today, week, month, or custom dates) and agent.
- Supports JSON output and UTC/local timezone filtering.
- No extra dependencies; works locally using your OpenClaw session logs.
Metadata
Frequently Asked Questions
What is Openrouter Usage?
Track OpenRouter API spending — credit balance, per-model cost breakdown, and spending projections from OpenClaw session logs. It is an AI Agent Skill for Claude Code / OpenClaw, with 421 downloads so far.
How do I install Openrouter Usage?
Run "/install openrouter-usage-info" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Openrouter Usage free?
Yes, Openrouter Usage is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Openrouter Usage support?
Openrouter Usage is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Openrouter Usage?
It is built and maintained by Luis Cajigas (@lcajigasm); the current version is v0.1.0.
More Skills