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

@developed-by-ms/prove-it

v0.0.6

Published

Verification-first workflow for AI coding agents. Never say done without proof.

Readme

prove-it

AI coding agents confidently ship broken code. prove-it fixes this.

MIT License npm Works with Claude Code Works with Cursor Works with Windsurf

Never say done without proof.

prove-it enforces a verification-first protocol on AI coding agents. Before claiming completion, the agent must state what "done" looks like, run the code, and show real output. Not "this should work" — actual evidence.


The problem

You: "Add null check to getUserProfile"

AI:  "I've added a null check to getUserProfile. The implementation looks
     correct and should handle the edge case properly. The code is ready."

No test was run. No output was shown. This ships with bugs.

Research shows AI coding agents produce 1.7× more bugs and have 60–80% failure rates on multi-step tasks. The root cause is not capability — it is protocol. Agents are never required to demonstrate evidence before saying done.


After prove-it

You: "Add null check to getUserProfile"

AI:
VERIFICATION PLAN
─────────────────
What done looks like: getUserProfile returns null safely when user not found
How I will verify:    npx jest --testPathPattern=getUserProfile
Edge cases:           null userId, user not in DB, DB unavailable

[implements code]

VERIFICATION RESULT
───────────────────
Command: npx jest --testPathPattern=getUserProfile
Output:
  ✓ returns null when userId is null (4ms)
  ✓ returns null when user not found (12ms)
  ✓ returns user object when found (8ms)
  Tests: 3 passed, 3 total
Status: PASS ✓

Install

Claude Code

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/MeenakshiSundaram-MS/prove-it/main/hooks/install.sh)

Windows:

irm https://raw.githubusercontent.com/MeenakshiSundaram-MS/prove-it/main/hooks/install.ps1 | iex

Installs SessionStart and UserPromptSubmit hooks into ~/.claude/settings.json. At session start, auto-detects your project's language and test framework, and emits a PROVE-IT ACTIVE context block. Adds a blue [PROVE-IT] badge to the status bar.

Confirm the install worked: npx @developed-by-ms/prove-it verify

Switch modes with /prove-it tdd, /prove-it strict, /prove-it off.

Cursor

npx @developed-by-ms/prove-it install

Copies three .mdc rule files to .cursor/rules/. prove-it.mdc is always-on. Toggle TDD and strict modes in Cursor Settings → Rules. Commit the files so your whole team gets them.

npx @developed-by-ms/prove-it install --global    # applies to all your projects
npx @developed-by-ms/prove-it install --force     # overwrite existing rules
npx @developed-by-ms/prove-it install --mode=tdd  # install core + TDD mode only

All platforms at once

If you use multiple AI tools in the same repo:

npx @developed-by-ms/prove-it install --all

Installs Cursor rules + Windsurf, Cline, Copilot, and Codex files in one command. Then commit everything:

git add .cursor .windsurf .clinerules .github/copilot-instructions.md .codex
git commit -m "chore: add prove-it verification rules"

Windsurf

mkdir -p .windsurf/rules
curl -fsSL https://raw.githubusercontent.com/MeenakshiSundaram-MS/prove-it/main/.windsurf/rules/prove-it.md \
  -o .windsurf/rules/prove-it.md
git add .windsurf/rules/prove-it.md && git commit -m "chore: add prove-it"

Cline

mkdir -p .clinerules
curl -fsSL https://raw.githubusercontent.com/MeenakshiSundaram-MS/prove-it/main/.clinerules/prove-it.md \
  -o .clinerules/prove-it.md
git add .clinerules/prove-it.md && git commit -m "chore: add prove-it"

GitHub Copilot

mkdir -p .github
curl -fsSL https://raw.githubusercontent.com/MeenakshiSundaram-MS/prove-it/main/.github/copilot-instructions.md \
  -o .github/copilot-instructions.md
git add .github/copilot-instructions.md && git commit -m "chore: add prove-it"

Applies to Copilot Chat (inline chat and chat panel). Requires workspace context to be enabled in VS Code.

Codex (OpenAI)

mkdir -p .codex
curl -fsSL https://raw.githubusercontent.com/MeenakshiSundaram-MS/prove-it/main/.codex/instructions.md \
  -o .codex/instructions.md
git add .codex/instructions.md && git commit -m "chore: add prove-it"

For detailed setup, verification steps, and mode switching for every platform, see AGENTS.md.


Modes

| Mode | When to use | What's required | |------|-------------|-----------------| | verify | Default, all coding | VERIFICATION PLAN before + VERIFICATION RESULT after | | tdd | New features, bug fixes | Write failing test (red), then implement (green) | | strict | Production, APIs, migrations | Compile ✓ + regression ✓ + new tests ✓ + edges ✓ |

Switch modes in Cursor's rules panel (toggle prove-it-tdd.mdc or prove-it-strict.mdc), or in Claude Code: /prove-it tdd, /prove-it strict, /prove-it off. See docs/modes.md for mode switching on all platforms.


Rule files

| File | Type | Description | |------|------|-------------| | prove-it.mdc | Always on | Core verification protocol — PLAN before, RESULT after | | prove-it-tdd.mdc | Toggle | TDD mode: failing test first, show red → green | | prove-it-strict.mdc | Toggle | 4-gate strict: compile + regression + new tests + edges |


Platform support

| Platform | Config file | Highlights | |----------|-------------|-----------| | Claude Code | ~/.claude/settings.json hooks | Auto-detects framework, /prove-it commands, statusline badge | | Cursor | .cursor/rules/*.mdc | UI toggle for TDD/strict modes, team-shareable via git | | Windsurf | .windsurf/rules/prove-it.md | trigger: always_on, team-shareable via git | | Cline | .clinerules/prove-it.md | Applies to every Cline task in the project | | GitHub Copilot | .github/copilot-instructions.md | Copilot Chat only (not inline completions) | | Codex | .codex/instructions.md | Applied as system instructions |


Language support

Auto-detected at session start (Claude Code) or inferred from project files:

| Language | Test command | Type-check | |----------|-------------|------------| | TypeScript | npx jest / npx vitest run / npm test | npx tsc --noEmit | | JavaScript | npx jest / npx vitest run / npm test | — | | Python | python -m pytest -v | mypy | | Go | go test ./... | go build ./... | | Rust | cargo test | (included) | | Java | mvn test -q / ./gradlew test | mvn compile -q | | Ruby | bundle exec rspec / minitest | — | | Unknown | Inline test generated and run | — |


Why not just add "write tests" to CLAUDE.md?

"Write tests" is advice. It drifts. An agent can rationalize it away, hedge around it, or silently skip it when under context pressure.

prove-it is a protocol with observable output. Every response that claims completion without a VERIFICATION RESULT block is visibly non-compliant. You can scan a conversation and see the violation.

Key differences:

| Generic advice | prove-it | |----------------|----------| | "Write tests before finishing" | Structured VERIFICATION PLAN block required before coding | | "Run the tests" | VERIFICATION RESULT block with pasted actual output required | | "Handle edge cases" | Gate 4 in strict mode: document or test null/empty/boundary | | No guidance for TDD | TDD mode enforces same test goes red then green | | No guidance when runtime unavailable | Explicit CANNOT VERIFY block with exact command + risk |

See docs/before-after.md for detailed comparisons.


Contributing

See CONTRIBUTING.md.

Rule improvements especially welcome — submit a skill_feedback issue with a before/after showing what the AI did vs. what it should have done.


Prior art

Inspired by JuliusBrussee/caveman — the token-compression skill that showed how structured rules change AI behavior reliably.