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

@kordra/cli

v0.1.31

Published

Kordra CLI — submit goals and run drones that auto-run dispatched tasks on your Claude subscription.

Vulnerabilities

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

Links

Git

Maintainers

kordradekordrade

Keywords

kordracliclaudedroneagentmcp

Readme

@kordra/cli

Kordra CLI — submit goals and run drones that auto-run the tasks you "Send to drones" in the Kordra console, on your own Claude subscription.

The version is PINNED below — a pinned tag means a future (or compromised) publish never auto-runs on your machine. Bump it deliberately.

Setup

npx @kordra/[email protected] login --token mx_...   # your seat token (Kordra console → Settings → Connect your Claude seat)

Run a drone

On any machine with claude logged in (it uses your Claude subscription, never an API key):

npx @kordra/[email protected] drone            # start once; auto-claims + runs dispatched tasks
npx @kordra/[email protected] drone --quota 5  # optional spend cap
npx @kordra/[email protected] drone status     # see the fleet

Requires git and claude on PATH. Needs ~/.kordrarc.json (written by login) or KORDRA_HUB_URL + KORDRA_TOKEN in the env.

Harness mode (best-of-N + verification media)

Opt in with KORDRA_HARNESS=1 and a claimed task is run through the best-of-N harness (triage → difficulty-rung generation → execution-based select → escalate) instead of a single worker. It files a verification report the console shows on the REVIEW card: the verdict, a per-candidate table, the winning diff, and a replay of the actual run.

KORDRA_HARNESS=1 kordra drone            # run claimed tasks through best-of-N

Nothing auto-ships — the result still lands in REVIEW for a human. The harness only auto-verifies with a validated fail-then-pass test; otherwise it suggests + routes to you.

Record a UI walkthrough (T4)

Give the drone a capture spec and the harness records a real video of the new UI (the actual app, driven headlessly) plus a backend-change brief, both shown on the card:

KORDRA_HARNESS=1 \
  KORDRA_CAPTURE_SERVE="<command to build+serve the app>" \
  KORDRA_CAPTURE_URL="http://localhost:<port>" \
  KORDRA_CAPTURE_STEPS='[{"caption":"open the new tab","click":"[data-tab=foo]","hold":2500}]' \
  kordra drone

A video (vs. a single screenshot) uses puppeteer-core (installed automatically as an optional dep; drives your INSTALLED Chrome — no Chromium download) and ffmpeg on PATH. Both degrade gracefully: no puppeteer-core → one still; no ffmpeg → a frame filmstrip. The serve command must point the app at a seeded/mock backend — never production secrets.