at-usage

Queries and displays current API provider balance and recent usage.

180|Updated Jul 7, 2026

Search Tags:#monitoring #cli #node.js #quota #billing #api usage #provider balance

Ready to run

npx skills add https://github.com/kairyou/agent-tools --skill at-usage-kairyou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: at-usage
Source: https://github.com/kairyou/agent-tools/tree/main/capabilities/usage/skills/at-usage
Command: npx skills add https://github.com/kairyou/agent-tools --skill at-usage-kairyou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It gives you a quick, direct view of your API provider's remaining balance and recent usage without leaving your coding agent session or logging into a web dashboard. ## Core Features & Use Cases - Balance Query: Runs a pre-installed local CLI to fetch the current API provider balance. - Usage Reporting: Displays recent usage statistics returned by the provider, verbatim and unmodified. - Use Case: Before starting a long agent session, ask for your provider usage to confirm you have sufficient balance and to review recent consumption. ## Quick Start Ask the agent to show my current API provider balance and recent usage.

Frequently Asked Questions about at-usage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I check my API provider balance from my coding agent?▼

Invoke the at-usage skill, which runs the installed local usage CLI with your agent identifier and returns the provider's balance and recent usage output directly. No manual dashboard login is required.

How to view recent API usage statistics in the terminal?▼

The skill executes a pre-installed Node.js CLI command that queries the provider and prints recent usage to stdout. The output is returned verbatim, exactly as the CLI produces it.

Does the usage query require installing extra packages?▼

No. The skill explicitly forbids running npx, npm, pnpm, or bun and never installs packages. It only runs the already-installed local usage command referenced by its configured path.

Why does the usage query say provider usage is unavailable?▼

That message appears when the local usage CLI returns empty stdout, meaning the provider returned no data or the query failed silently. Verify the CLI is installed correctly and your provider credentials are configured.

Can I use a different script to check provider usage?▼

No. The skill is restricted to the single installed command defined at setup and will not substitute alternative usage scripts. This ensures consistent, trusted output from the configured provider integration.