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

human-steerkit

v0.2.3

Published

Human steers. Agent builds. The AI agent starter kit.

Readme

🧭 human-steerkit


Stop Burning AI Credits on Wasted Context

Every wasted agent credit traces back to the same root causes: the agent re-discovers scope it was never told, scans files it did not need to read, debates architecture mid-task, and receives a vague prompt that turns into long back-and-forth.

human-steerkit eliminates all of these before the agent starts — turning your project into a sequence of bounded, file-scoped prompts the agent can execute without guessing.

  • hsk init: Answer 6 questions. Lock scope before the agent starts — project goal, stack, budget, and a full task list pre-filled from your chosen template.
  • hsk next: Output a bounded, file-scoped prompt for the next pending task. The agent knows exactly what to read, what to build, and what not to touch.
  • hsk done / hsk spend: Track progress and credit cost task-by-task. No API connections — the developer stays in control of every decision.

How the flow works

npm install -g human-steerkit
         │
         ▼
    hsk init          ← lock scope: name, goal, stack, budget, tasks
         │
         ▼
    hsk next          ← get a bounded, file-scoped prompt for task 1
         │
         ▼
  paste into agent    ← Claude Code / Cursor / Copilot / Codex
         │
         ▼
    hsk done 1        ← mark complete
    hsk spend 1 8     ← record credits used
         │
         ▼
    hsk next          ← repeat for task 2, 3 … n
         │
         ▼
    hsk status        ← see progress + budget at any time
    hsk report        ← full per-task breakdown when done

Demo

hsk demo

Installation

npm install -g human-steerkit

Or use without installing:

npx human-steerkit init

Quick start

hsk init                      # answer 6 questions, scaffold your project files
hsk next                      # get a bounded prompt for the next pending task
hsk next --copy               # same, and copy the prompt straight to clipboard
# paste prompt into your agent, run the task
hsk done 1                    # mark task 1 complete
hsk spend 1 12                # record 12 credits used on task 1
hsk status                    # see progress and budget summary
hsk report                    # per-task credit breakdown: estimates vs actuals

How it works

  1. hsk init asks 6 questions (project name, goal, stack, agent tool, budget, task count) and generates PROJECT.md, TASKS.md, DECISIONS.md, and PROMPTS.md in your project root — pre-filled with your answers and a task list from your chosen template.

  2. hsk next reads your TASKS.md, finds the first unchecked task, and outputs a ready-to-paste prompt in a fixed format: the exact files to read, the task description, the expected output, and a constraints block that prevents the agent from over-generating.

  3. You run one task at a time. Mark it done with hsk done <n>, record the credit cost with hsk spend <n> <credits>, and repeat. hsk check scans for patterns that waste credits before you hand off to the agent.

Commands

| Command | Description | |---|---| | hsk init | Interactive wizard — scaffolds project files and folder structure | | hsk task <n> | Generate bounded agent prompt for task number n | | hsk task <n> --copy | Generate prompt and copy it to clipboard | | hsk next | Find first pending task and output its prompt | | hsk next --copy | Find next task, output prompt, and copy to clipboard | | hsk add | Interactively add a new task to TASKS.md | | hsk done <n> | Mark task n complete in TASKS.md | | hsk status | Show task progress and budget summary | | hsk report | Per-task credit breakdown: estimates vs actuals | | hsk check | Scan project for credit-wasting patterns | | hsk spend <n> <credits> | Record actual credits used for task n | | hsk budget <total> | Set total credit budget |

Templates

| Template | Stack | Tasks | |---|---|---| | fullstack-py | Next.js + FastAPI + SQLite | 20 | | nextjs-app-router | Next.js App Router + Prisma + TypeScript | 12 | | nextjs-api | Next.js + API Routes + TypeScript | 14 | | supabase | Next.js App Router + Supabase | 12 | | fastapi-only | FastAPI + SQLite | 12 | | express-api | Node.js + Express + SQLite | 12 | | blank | Any stack | 0 |

Credit waste checker

hsk check scans PROJECT.md, DECISIONS.md, TASKS.md, and PROMPTS.md for these patterns:

| Rule | Problem | Fix | |---|---|---| | PROJECT_MISSING | Agent re-discovers scope every session | Run hsk init | | DECISIONS_MISSING | Agent debates architecture mid-task | Run hsk init | | TASKS_MISSING | No task sequence — agent decides what to do | Run hsk init | | TASK_MISSING_READS | Agent scans whatever files it finds | Add reads field to task | | TASK_READS_TOO_BROAD | reads: src/ causes full codebase scan | Narrow to specific files | | TASK_READS_TOO_MANY | More than 8 files — context too large | Split task into two | | TASK_DESCRIPTION_TOO_SHORT | Agent asks clarifying questions | Expand description | | PROMPTS_MISSING_CONSTRAINTS | Agent over-generates output | Add constraints block |

Philosophy

  • Human plans, agent executes. Architecture decisions, task sequence, and file scope are locked before the agent touches any code. The agent never decides what to do next.
  • Bounded context. Every prompt lists only the files the agent needs to read. No src/, no root directories, no open-ended exploration.
  • Manual tracking by design. Credits and progress are tracked manually. No API connections, no automatic monitoring — the developer stays in control of every decision.

Contributing

Contributions are welcome. The fastest way to contribute is to add a new stack template — templates are plain JSON files in src/templates/ that follow a simple schema. No TypeScript required. Copy an existing template, fill in the task list for your stack, and open a pull request.

License

MIT