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

oh-my-grok

v0.1.0

Published

Tiny omg wrapper that makes Grok Build stop asking and keep building.

Downloads

124

Readme

oh-my-grok

oh-my-grok ships omg, a tiny wrapper around xAI's grok / Grok Build CLI.

It is intentionally small: it injects an autonomy rule block, disables Grok plan approval by default, and starts trusted sessions in always-approve mode so the agent stops re-asking obvious questions and keeps building.

Why

Grok Build already supports the important surfaces:

  • --rules to append session instructions.
  • AGENTS.md / Agents.md project rules.
  • --no-plan to avoid plan-mode approval stops.
  • --always-approve to avoid tool permission stops in trusted repos.

omg just composes those into one command with an opinionated “그만 물어보고 좀 가자” rule set.

Install

After publish:

npm install -g oh-my-grok

From this checkout:

npm link

Requires Node.js 18+ and the official grok command on PATH.

Usage

omg "fix the failing test and verify it"

Equivalent shape:

grok --rules "$(cat rules/omg.md)" --no-plan --always-approve -p "fix the failing test and verify it"

Open the normal Grok TUI with the same defaults:

omg

Keep tool approvals on:

omg --ask "review this repo without changing files"

Keep Grok plan mode available:

omg --plan "design a larger migration"

Inspect what would run:

omg --dry-run --cwd ~/repo "ship the smallest safe patch"
omg --print-rules

Safety

By default omg adds --always-approve, which lets Grok execute tools without permission prompts. Use it only in trusted repositories. Use --ask / --careful when you want Grok to keep approval prompts.

The injected rules still instruct Grok to ask for destructive, irreversible, credential-gated, external deploy/publish/send/purchase, or materially scope-changing actions.

Development

npm test
npm run pack:check