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

@0xray/grok-bot

v0.1.9

Published

Complete setup path for Grok Bot agents on 0xRay: per-agent suits, Groover identity, OWS pay, hangar shops. Seat doctor/ready proves mill+inspect and prints hangar/Clearing next steps.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

htafollahtafolla

Keywords

grok-bot0xraymillsuitgrooverhangaragentsdoctor

Readme

@0xray/grok-bot

Start here

Read first: OP-PROC.md — the one-page operating procedure.

Board: house/WAVEBOARD.md and house/ATTENTION_STATE.md (your project house, not in this package). If house/ is missing, run npx @0xray/grok-bot house init (skill setup-house). It copies templates/house/ and refuses to overwrite. house init --migrate moves an old ops/WAVEBOARD.md into house/WAVEBOARD.md and starts ATTENTION_STATE.md. Complete setup path for Grok Bot agents on the 0xRay mill.

Agents: read llms.txt → AGENTS.md → run skills in SKILLS.md (one suit per key agent).
Humans: same files.

Install

npm i @0xray/grok-bot
npx @0xray/grok-bot

Seat doctor (prove plant)

From an agent project root:

npx @0xray/grok-bot doctor
npx @0xray/grok-bot ready          # same command
npx @0xray/grok-bot doctor --json

Plain: this checks that mill + inspect are fastened on this seat, says whether Repertoire and Open Wallet (~/.ows) are present, then prints what to do next for hangar shops and Clearing (402 / USDC on Base). A HOUSE.md line that is exactly wallet off skips those wallet steps. It does not mill-plant Clearing into 0xRay. Product MCP name is clearing, never xray-clearing.

House lookup: GROK_BOT_HOUSE (the house directory or its HOUSE.md) wins. If that variable is unset, doctor walks up from the working directory for house/HOUSE.md. A set path that is missing warns and does not walk. No house file warns. Unfilled example lines fail.

Path (per agent)

  1. Suit — mill + inspect (fasten-suit-per-agent)
  2. Identity — Groover register → mint → pin (groover-factory-parity) when needed
  3. Pay — OWS wallet + Base USDC (setup-ows-pay)
  4. Hangar — plant shops (plant-hangar-shops)

Plant pins (monitor / adjust)

  • 0xray (current npm) · mill nested in the tarball (npx @0xray/foundry)
  • Live URLs in llms.txt

This package orchestrates. It does not vendor the whole OS.

Fleet ops

Read house/ first (this team's board and rules). If house/ is missing, run grok-bot house init to copy templates/house/. Longer notes under ops/ stay in the git repo and are not in the npm package.