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

@bixai/god-of-debugger

v0.5.1

Published

Hypothesis-driven parallel debugging plugin for Claude Code. Generates competing hypotheses, runs experiments in parallel subagents, ships a fix only when exactly one survives.

Readme

god-of-debugger

npm version Node.js License: MIT

Falsification-first, hypothesis-driven parallel debugging — ships to Claude Code, Cursor, Codex CLI, Continue.dev, and any open-plugins-compatible host.

Website: godofdebugger.bixai.dev · Repo: github.com/soummyaanon/god-of-debugger · Plugin docs: plugins/god-of-debugger/README.md


How it works

  1. You describe the bug (repro, logs, expected vs actual).
  2. The plugin generates competing hypotheses across different causal axes—not one “best guess.”
  3. hypothesis-runner subagents run in parallel, each executing one falsifiable experiment and returning a strict verdict: killed, survived, or inconclusive.
  4. Results roll up into a survival table so you see what evidence actually supports.
  5. When you ship a fix, guards and promote flows help turn surviving experiments into regression coverage instead of one-off debugging.

Think: scientific method + parallel agents, not a single linear “try this, try that” chat.


Supported agents

| Host | Surface | Install command | Parallel subagents | Ship-the-fix hook | |------|---------|-----------------|:------------------:|:-----------------:| | Claude Code | native plugin | god install | yes | yes (PreToolUse) | | Cursor | .cursor/rules/god-of-debugger.mdc | god install --host=cursor | no (sequential fallback) | prose rule | | Codex CLI | AGENTS.md at repo root | god install --host=codex | no | prose rule | | Continue.dev | .continue/config.yaml | god install --host=continue | no | prose rule | | open-plugins | .plugin/ bundle | god install --host=open | host-dependent | host-dependent |

On hosts without PreToolUse hooks, the "don't propose a fix unless exactly one hypothesis survived" rule is enforced as a prose rule the model must self-police.

Short usage guide: USAGE.md.

Install — interactive picker (easiest)

If you don't remember host flags, just run:

npm i -g @bixai/god-of-debugger
god install

An arrow-key picker appears:

Pick a host to install god-of-debugger:
❯ Claude Code   native plugin · parallel subagents · PreToolUse hook
  Cursor        writes .cursor/rules/god-of-debugger.mdc
  Codex CLI     writes ./AGENTS.md
  Continue.dev  writes .continue/config.yaml
  open-plugins  copies ./.plugin/ bundle into project
↑/↓ move · enter select · q/ctrl-c cancel

Navigate with / (or j/k, or number keys 1-5), press Enter to install. Ctrl-C or q to cancel. In a non-TTY environment (CI, piped input), it silently defaults to claude; add -y to force non-interactive mode.

Install (Claude Code — npm, recommended)

Install the CLI globally, sync the plugin into Claude Code, then restart Claude Code so the plugin loads.

npm i -g @bixai/god-of-debugger
god install

After restart, invoke the workflow from Claude Code with:

/god-of-debugger:go

Other package managers

Same flow: global install → god install → restart Claude Code.

| Manager | Command | |--------|---------| | pnpm | pnpm add -g @bixai/god-of-debugger && god install | | yarn | yarn global add @bixai/god-of-debugger && god install | | bun | bun add -g @bixai/god-of-debugger && god install |

No global install (npx)

npx @bixai/god-of-debugger install

Still restart Claude Code after install so the plugin is picked up.

CLI maintenance

| Command | What it does | |---------|----------------| | god update | Refresh the installed plugin from the package | | god uninstall | Remove the plugin from Claude Code | | god doctor | Quick health check |


Install (Cursor)

npm i -g @bixai/god-of-debugger
cd /path/to/your/project
god install --host=cursor

Drops .cursor/rules/god-of-debugger.mdc into the project.

Then in Cursor:

  1. Reload the window.
  2. Open Cursor Settings → Rules and confirm god-of-debugger is listed.
  3. In chat, paste a stack trace or describe the bug. Or force it: @god-of-debugger debug this failing test.

Cursor has no subagent dispatch, so experiments run sequentially. The S==1 fix-refusal rule is enforced as prose.

Install (Codex CLI)

npm i -g @bixai/god-of-debugger
cd /path/to/your/project
god install --host=codex

Drops AGENTS.md at the project root. Codex reads it on every session from that dir.

codex
> debug this: npm test -- auth.spec.ts

If an AGENTS.md already exists, the installer refuses to clobber — merge the god-of-debugger section manually.

Install (Continue.dev)

npm i -g @bixai/god-of-debugger
cd /path/to/your/project
god install --host=continue

Writes .continue/config.yaml with a /god-of-debugger slash prompt + rule.

Then in Continue's chat panel:

/god-of-debugger login endpoint returns 500 on valid creds

Install (open-plugins host)

cd /path/to/your/project
god install --host=open

Copies the .plugin/ bundle into the project. Any open-plugins-compliant host picks it up from there.

No-install path (npx) — any host

npx @bixai/god-of-debugger install --host=cursor
npx @bixai/god-of-debugger install --host=codex
npx @bixai/god-of-debugger install --host=continue
npx @bixai/god-of-debugger install --host=open

Uninstall per host

god uninstall                    # Claude Code
god uninstall --host=cursor      # removes .cursor/rules/god-of-debugger.mdc
god uninstall --host=codex       # removes AGENTS.md
god uninstall --host=continue    # removes .continue/config.yaml
god uninstall --host=open        # removes .plugin/

Run god doctor any time to see which hosts are installed.


Install (Claude marketplace)

If you prefer the marketplace flow instead of npm:

claude plugin marketplace add soummyaanon/god-of-debugger
claude plugin install god-of-debugger@soumyapanda-cc-marketplace

In a Claude Code session:

/plugin marketplace add soummyaanon/god-of-debugger
/plugin install god-of-debugger@soumyapanda-cc-marketplace

Versioning

Community

License

MIT. See LICENSE.