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

kokoro-polish

v0.2.0

Published

After your AI has built the app, have Claude Fable read check.html against your spec and write kokoro-fixes.md: the holes it found, heaviest first, with how to fix them. Opt-in, uses your own Anthropic API key.

Readme

kokoro-polish

After your AI has built the app, have Claude Fable read it. You get kokoro-fixes.md: the holes it found, heaviest first, each with why and how to fix it — ready to hand back to your AI.

export ANTHROPIC_API_KEY=sk-ant-...
npx kokoro-polish            # reads ./check.html (+ ./kokoro-spec.md if present)

Easiest: ask your AI to run it

No terminal skills needed. If you build with an AI coding tool (Claude Code etc.), ask it like this — it keeps the "ask before sending" step with you:

Before sending anything, ask me first. When I say yes, run npx kokoro-polish --yes in this project and show me kokoro-fixes.md.

Needs your Anthropic API key on your machine (ANTHROPIC_API_KEY). Set it once in your system's environment variables, then restart your AI tool — Windows: search "environment variables" in Settings; macOS/Linux: add export ANTHROPIC_API_KEY=... to ~/.zshrc or ~/.bashrc. ★Do not paste your key into the AI chat — it stays in the conversation history.

The command above is for running it yourself in a terminal.

  • Reads check.html against your spec. check.html is the unminified single-file copy that a kokoro-baton spec asks your AI to create. With the spec, it also finds where the app differs from what you decided.
  • You get a list of fixes, not rewritten code. check.html is a copy, so fixing it would not fix your app. Give kokoro-fixes.md to your AI (Claude Code etc.) to fix the main app, then check by actually using it (npx kokoro-aegis .).
  • Only when you choose it. It shows what will be sent, where, and roughly what it costs — and asks before sending anything (--yes skips the question).
  • Your code goes straight from your machine to Anthropic — not through the Kokoro OS server — and is not stored.
  • Billed to your key: roughly $0.70–$1.00 per run, 2–4 minutes. --effort low is faster and cheaper; --no-spec leaves the spec out.
  • It only reads — nobody presses anything. Each finding still has to be checked by running the app.

Options: [check.html] --spec <file> --no-spec --effort low|medium|high --yes --out kokoro-fixes.md --lang ja|en

Related: decide before you build with kokoro-baton; get a hand-check table without any AI with kokoro-aegis (it never sends your code).

License

PolyForm Shield 1.0.0 — free to use for any purpose, including at work and commercially. You may not use it to build a product that competes with it.


日本語

AI に作ってもらったあとで、Claude Fable にコードを読ませる道具です。 見つけた穴が重い順に、理由と直し方つきで並んだ kokoro-fixes.md(直してほしいことの紙) ができます。

npx kokoro-polish            # このフォルダの check.html(と kokoro-spec.md があればそれも)を読む

いちばん簡単な使い方:AI に頼む

ターミナルの操作が分からなくても使えます。Claude Code などの AI と一緒に作っているなら、その AI にこう頼んでください。「送る前に聞く」を、AI が勝手に済ませないようにする頼み方です。

送る前に、必ず私に聞いてください。私が「送って」と言ったら、このプロジェクトのフォルダで npx kokoro-polish --yes を実行して、できた kokoro-fixes.md を見せてください。

あなたの Anthropic の API キーが、パソコンに入っている必要があります(ANTHROPIC_API_KEY)。一度だけ入れておき、AI の道具を開き直してください。Windows:設定で「環境変数」と検索 →「アカウントの環境変数を編集」で新しく足す。Mac:~/.zshrc に export ANTHROPIC_API_KEY=... を足す。★キーを AI との会話に貼らないでください(会話の記録に残ります)。

上のコマンドは、ターミナルで自分で打つ人向けです。

  • 読むのは check.html(kokoro-baton の指示書が作る AI に置かせる、圧縮していない 1 枚の写し)と仕様の紙です。仕様の紙があると、決めたことと食い違っているところも見つけます。
  • 返すのは直したコードではなく、直してほしいことの紙です。check.html は写しなので、写しを直しても本体は直りません。紙を作った AI(Claude Code など)に渡して、本体を直してもらいます。直したら npx kokoro-aegis . で、動かして確かめます。
  • 選んだときだけ動きます。 何をどこへ送るか・費用の目安を出して、送る前に必ず聞きます(--yes で省けます)。
  • コードは あなたのパソコンから直接 Anthropic に送られます(Kokoro OS のサーバーは通りません)。保存はしません。
  • 費用はあなたのキーに付きます(1 回 100〜150 円ほど・2〜4 分)。--effort low で速く安くなります。--no-spec で仕様の紙を外せます。
  • 読むだけで、押してはいません。見つけたことは、動かして確かめる必要があります。
  • kokoro-aegis は AI を使わず、コードもどこにも送りません。AI に読ませたいときだけ、この道具を使います。

使ってよい範囲:PolyForm Shield 1.0.0。仕事でも商売でも自由に使えます。これと競合する製品を作るために使うことはできません。