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

@fibilisim/leanagents

v0.1.0-alpha.3

Published

Selective coding workflows with context budgets, bounded TypeScript fixes, and recorded test and review results.

Readme

LeanAgents

Load only the expertise your coding task actually needs.

CI

Active development · v0.1.0-alpha.2 · MIT

LeanAgents is a selective coding workflow for AI coding assistants. It uses explicit task scope and risk to load only the instructions, references and review steps a task actually needs.

The current alpha includes a TypeScript reviewer, bounded fix workflow, context preparation, routing and target-specific exports. Codex is the only runtime currently exercised with a real CLI; Kiro, Cursor and Antigravity exports are format-verified but not yet validated in native editor runs.

Why LeanAgents?

  • Selective by default: simple work stays with the host; extra review is added only when needed.
  • Context on demand: shared instructions are assembled once; longer references stay separate until selected.
  • Verification before apply: candidate fixes are tested and reviewed before they can be applied.
  • Recorded evidence: source hashes, usage records and run results are kept for bounded workflows.
  • Quality before prompt size: safety and correctness requirements are not silently removed to shrink context.

Current support

| Capability | Status | Notes | | --- | --- | --- | | Task routing | ✅ Implemented | Explicit scope and risk produce the plan | | Context preparation | ✅ Implemented | Selected instructions plus manifest and hashes | | TypeScript review | ✅ Codex CLI tested | Explicit files reviewed through an authenticated Codex CLI | | Bounded TypeScript fix | ✅ Implemented | Candidate → tests → separate review → guarded apply | | Codex export | ✅ Bootstrap verified | Real CLI bootstrap loading checked | | Kiro export | 🟡 Format verified | Native execution not yet verified | | Cursor export | 🟡 Format verified | Native execution not yet verified | | Antigravity export | 🟡 Format verified | Native execution not yet verified | | Additional specialist agents | ⏳ Planned | Added only when measured failures justify them |

See adapter support and activation.

Quick start

Runtime: Node.js 22.12+. Development: Node.js 22.13+ or 24+.

Run inside your project (no clone or build required):

npx @fibilisim/leanagents setup --target codex

Replace codex with kiro, cursor, or antigravity. Omit --target for an editor selection menu. Use --dry-run to preview or --dir for another project. Setup preserves existing Codex instructions with a marked block and backup. Conflicting files stop setup before writes. Repeating setup does not duplicate it.

Published on npm as @fibilisim/leanagents. Run npx @fibilisim/leanagents setup for the interactive editor menu. Antigravity setup writes an Always On workspace rule (trigger: always_on); no manual activation is required for new installations. Native agent execution remains unverified.

Development from source

git clone https://github.com/Fibilisim-Tekno/leanagents.git
cd leanagents
npm ci
npm run build
node dist/bin.js --help
node dist/bin.js check

Offline commands do not call a model. Review and fix commands use the installed Codex CLI and consume the authenticated account's quota.

Export for Codex

node dist/bin.js export --target codex --out ../leanagents-codex

Other generated bundles:

node dist/bin.js export --target kiro --out ../leanagents-kiro
node dist/bin.js export --target cursor --out ../leanagents-cursor
node dist/bin.js export --target antigravity --out ../leanagents-antigravity

The destination must be new. Existing editor settings are never overwritten.

Try a bounded fix

The supplied example intentionally contains a defect.

node dist/bin.js fix --repo examples/batch-fix --spec examples/batch-fix/task.json --out ../leanagents-run --model YOUR_MODEL_ID
node dist/bin.js apply --repo examples/batch-fix --run ../leanagents-run

On Windows, --codex-js can point to the installed Codex CLI JavaScript entrypoint. The fix command preserves original files; apply is a separate modification step. See workflow constraints and instructions.

Core workflow

  1. Route — build a selection plan from explicit task facts and risk.
  2. Prepare — assemble the selected instructions, references and manifest.
  3. Review or fix — use the bounded Codex-backed workflow for explicit TypeScript files.
  4. Verify — run the supplied tests and obtain a separate review where required.
  5. Apply — re-check source hashes before modifying the working copy.

Verification

  • 173 local tests pass together with type checking, lint and compilation.
  • GitHub Actions checks Ubuntu and Windows on Node 22 and 24.
  • A constructed reviewer smoke test found a known TypeScript defect and produced no finding after the host-side correction.
  • A constructed bounded-fix smoke test moved from two failing tests to 3/3 passing, then passed a separate review and guarded apply.
  • Codex bootstrap loading was checked with the real CLI.

These results demonstrate integration behavior. They do not establish general quality, lower total model usage, or superiority over ECC or another toolkit.

Evaluation evidence

| Document | Purpose | | --- | --- | | Evaluation methodology | Defines fair comparison, held-out-task, usage-accounting and scoring rules | | Initial instruction-only pilot | Small three-arm prompt-only pilot; not a full workflow benchmark | | Reviewer smoke test | Known-defect review integration using the Codex CLI | | Automatic fix smoke test | Candidate generation, tests, separate review and guarded apply |

Scope and limits

The current fix runner supports explicit, dependency-free TypeScript snapshots. LeanAgents is not yet a general autonomous repository editor. Test programs execute locally; the working copy is not an operating-system sandbox. The reviewer can miss defects, and passing supplied tests proves only those tested behaviors.

Catalog size, assembled instruction size and actual model usage are different measurements. Cached input is not added twice. Smaller startup text is not, by itself, evidence of lower total cost or better code.

Roadmap

  1. Validate native editor workflows and context loading in Kiro, Cursor and Antigravity.
  2. Evaluate held-out tasks with comparable model and tool settings.
  3. Extend language and specialist coverage only where measured failures justify it.
  4. Improve installation, recovery, packaging and release ergonomics.

Development

npm run check:all
npm run build
node dist/bin.js check

See CONTRIBUTING.md, SECURITY.md, CHANGELOG.md and the bench/ directory. Licensed under MIT.