npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

opencode-usage-plugin

v0.0.2

Published

OpenCode plugin to display subscription usages for OpenAI, Google, and z.ai

Readme

opencode-usage-plugin

OpenCode plugin that fetches subscription usage for OpenAI, Google, and z.ai.

Features

  • /usage command for all providers
  • /usage <provider> for a single provider
  • Returns normalized JSON for provider usage
  • Reads tokens from OpenCode and auth plugins

Installation in OpenCode

Create or edit ~/.config/opencode/opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["[email protected]"]
}

For local development, use a relative path:

{
  "plugin": ["./path/to/opencode-usage-plugin"]
}

Provider Setup

OpenAI

  • Install the opencode-openai-codex-auth plugin, or ensure openai auth exists in ~/.local/share/opencode/auth.json (aliases: codex, chatgpt).
  • The plugin also checks ~/.opencode/auth/openai.json as a fallback.

Google

  • Install an Antigravity auth plugin (for example, opencode-antigravity-auth) or ensure google auth exists in ~/.local/share/opencode/auth.json (alias: antigravity).
  • Ensure accounts are stored in ~/.config/opencode/antigravity-accounts.json.
  • The activeIndex account is used for usage checks (falls back to the first account).

z.ai

  • Add a zai-coding-plan entry in ~/.local/share/opencode/auth.json with the API key (aliases: zai, z.ai), or set ZAI_API_KEY.

Usage

/usage
/usage openai
/usage google
/usage zai-coding-plan

Output

  • usage tool returns a JSON array (string) of provider usage results
  • command/usage.md formats a human-readable summary

Development

npm install
mise run build
npm test
mise run lint

Testing

Tests use vitest with a provider-specific auth configuration system.

Run all tests (mocks only, default):

npm test

Run tests with real auth:

# Edit .env.test and set desired provider(s) to 1
TEST_REAL_OPENAI_AUTH=1
TEST_REAL_GOOGLE_AUTH=1
TEST_REAL_ZAI_CODING_PLAN_AUTH=1
npm test

Run specific provider tests:

npm test -- src/providers/openai/fetch.test.ts
npm test -- src/providers/google/fetch.test.ts
npm test -- src/providers/zai-coding-plan/fetch.test.ts

Test structure:

  • src/providers/common/test-helpers.ts - Shared test utilities and fixtures
  • src/providers/*/*.test.ts - Provider-specific tests with mocks and real auth
  • .env.test - Auth configuration flags (committed to repo)
  • vitest.config.ts - Test configuration

Tests are organized into two categories per provider:

  • Mock tests - Run by default, test all edge cases and error handling
  • Real auth tests - Skipped by default, enabled via .env.test flags

Adding new providers:

  1. Implement provider function in src/providers/
  2. Add TEST_REAL_NEWPROVIDER_AUTH=0 to .env.test
  3. Create src/providers/newprovider.test.ts following existing patterns
  4. Add helpers to src/test-helpers.ts if needed

Author

Nelson Pires [email protected]

Repository

https://github.com/nelsonPires5/opencode-usage-plugin

License

MIT License. See the LICENSE file for details.