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

@counted/claude-code

v0.1.1

Published

Counted analytics hooks for Claude Code — track AI agent actions privately

Downloads

242

Readme

@counted/claude-code

Privacy-first analytics for Claude Code hooks. Track AI agent actions without exposing code or content.

Install

npm install @counted/claude-code @counted/sdk

Usage

import { init, trackToolUse, trackFileEdit, trackCommand, trackSessionStart, trackSessionEnd } from "@counted/claude-code";

// Initialize once
init({ projectKey: "ck_..." });

// Track events
trackSessionStart({ model: "claude-sonnet-4-6", mode: "agent" });
trackToolUse({ tool: "Read", outcome: "success", durationMs: 120 });
trackFileEdit({ filePath: "src/index.ts", action: "edit", language: "typescript" });
trackCommand({ command: "npm test", exitCode: 0, durationMs: 5400 });
trackSessionEnd({ durationMs: 180000, toolUseCount: 42, fileEditCount: 8 });

What it tracks

  • Tool use: which tool was used, whether it succeeded, how long it took
  • File edits: which files were created/edited/deleted, what language
  • Commands: which commands were run, exit codes, duration
  • Sessions: start/end, model, mode, duration, counts

What it does NOT track

  • File contents or diffs
  • Command arguments or output
  • Prompt text or AI responses
  • Any personally identifiable information

Session handling

Sessions in agent contexts are different from browser sessions. The SDK is configured with sessionTimeout: 0 — sessions never auto-reset. You control session boundaries explicitly via trackSessionStart / trackSessionEnd.

Compare agent setups

Every event carries a setup fingerprint so you can break metrics down by agentic configuration ("setup A errors 2× more than setup B"):

  • setupHash — a stable digest of your setup: model, prompts (CLAUDE.md, .claude/agents/*), and tools/permissions (.claude/settings.json, permission_mode). Only the digest is sent — prompt content never leaves the machine. setupHashVersion tracks the scheme.
  • model — sent in the clear (low-sensitivity), so breakdowns are readable.
  • setupLabel — optional human bucket; set COUNTED_SETUP_LABEL="reviewer-v2".

In Counted, add a breakdown insight grouped by setupHash (or setupLabel) over tool_use outcome, command_run exit codes, or file_edit volume.

License

MIT