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

@llmtracer/openclaw

v1.0.1

Published

See where your AI budget goes.

Downloads

184

Readme

@llmtracer/openclaw

See where your AI budget goes.

Install

openclaw plugins install @llmtracer/openclaw

Configure

Add to ~/.openclaw/openclaw.json:

{
  "plugins": {
    "entries": {
      "llmtracer": {
        "enabled": true,
        "config": {
          "apiKey": "lt_your_key_here"
        }
      }
    }
  }
}

Get your API key at dashboard.llmtracer.com/signup.

Alternative: Set the LLMTRACER_API_KEY environment variable instead of putting the key in the config file. If running via systemd:

systemctl --user set-environment LLMTRACER_API_KEY="lt_your_key_here"
systemctl --user restart openclaw-gateway.service

Restart

# If running via systemd (typical):
systemctl --user restart openclaw-gateway.service

# If running directly:
# Stop the gateway (Ctrl+C) and restart it
openclaw gateway

Verify

openclaw agent -m "hello" --agent main

With "debug": true in the plugin config, you should see:

[llmtracer] ✓ Cost tracking active → dashboard.llmtracer.com
[llmtracer] openai/gpt-5-mini  XXX→XXX tokens  $X.XXXX  X.Xs

Open your dashboard at dashboard.llmtracer.com to see cost, latency, and usage.

Troubleshooting

"plugin manifest not found" — Your plugin version is outdated. Reinstall:

openclaw plugins uninstall llmtracer
openclaw plugins install @llmtracer/openclaw

"No API key" — The plugin couldn't find your key. Ensure either:

  • plugins.entries.llmtracer.config.apiKey is set in openclaw.json, OR
  • LLMTRACER_API_KEY env var is set in the gateway's environment

Gateway auth errors after install — If openclaw gateway install overwrote your service file, your existing env vars (like OPENAI_API_KEY) may be missing. Re-add them:

systemctl --user set-environment OPENAI_API_KEY="sk-..."
systemctl --user restart openclaw-gateway.service

What data is collected

  • Provider name (anthropic, openai, google)
  • Model name
  • Input and output token counts
  • Response latency
  • Tool names invoked (e.g. bash, browser, read)
  • SDK version and session ID (random UUID, not correlated to OpenClaw sessions)
  • Caller file path and line number

Not collected: message content, system prompts, conversation history, tool inputs/outputs, OpenClaw session IDs, user identifiers.