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

@jagit/hook-codex

v0.0.8

Published

Reports per-session OpenAI Codex CLI usage to JaGit.

Readme

@jagit/hook-codex

Reports per-session OpenAI Codex CLI usage to JaGit.

Setup (recommended — native Codex hook)

Codex CLI has a built-in hook mechanism. Add a Stop hook to ~/.codex/hooks.json (user-level) or .codex/hooks.json (repo-level):

{
  "hooks": {
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "JAGIT_BASE_URL=https://your-jagit-host JAGIT_API_KEY=<your-token> npx -y @jagit/hook-codex",
            "timeout": 30
          }
        ]
      }
    ]
  }
}

Codex passes the session payload on stdin (including session_id, model, cwd, transcript_path, and stop_hook_active). The hook reads token usage from the transcript and reports the session to JaGit. The stop_hook_active guard prevents duplicate reports when Codex re-runs the hook after a continuation.

Setup (legacy — shell wrapper)

If you are on an older Codex CLI version without hook support, install a shell function that wraps the real codex binary and reports after each session ends:

codex() {
  command codex "$@"
  local exit_code=$?
  npx -y @jagit/hook-codex >/dev/null 2>&1 || true
  return $exit_code
}

Add that function to your shell rc (~/.zshrc, ~/.bashrc, etc.). On exit, the reporter locates the most-recently-modified file under ~/.codex/sessions/**/*.jsonl, parses it, and posts the session summary.

You can also point the reporter at a specific transcript:

jagit-hook-codex --file ~/.codex/sessions/2026/06/20/rollout-...jsonl

Environment

export JAGIT_BASE_URL="https://your-jagit-host"
export JAGIT_API_KEY="<your DASHBOARD_API_TOKEN>"

Identity defaults to git config user.email (read from the session's cwd); override with JAGIT_GIT_USERNAME.

Notes

  • In native hook mode, model is read directly from the Codex stdin payload.
  • In legacy mode, model is parsed from turn_context records in the JSONL file.
  • Token counts in legacy mode are cumulative per Codex session; the reporter reads the last non-null token_count event, not a sum across events.
  • In native hook mode, token counts are summed across all assistant transcript entries (each entry represents one turn).
  • costUsd is always null — Codex logs do not expose a cost field.