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

@upgpt/upcommander

v0.2.2

Published

AI coding orchestrator. CONTRACT.md + codebase index + model routing. -85% cost validated across 52+ controlled runs.

Downloads

258

Readme

UpCommander

Multi-agent AI coding orchestrator. Reduce cost 85% and raise quality from 5/10 to 9/10 — validated across 49+ controlled benchmark runs.

The core insight: What you tell the AI before it starts matters more than the model, tool, or parallelism. UpCommander generates a structured brief (CONTRACT.md) before any worker touches code. That single change accounts for 54% of the total cost reduction.


Benchmark Results

| Approach | Cost | Quality | |----------|------|---------| | Naive baseline (no optimization) | $5.45 | 5/10 | | + CONTRACT.md brief | $2.51 | 9/10 | | + AST index compression | $0.85 | 9/10 | | + Haiku orchestrator | $0.83 | 9/10 |

-85% cost. Quality from 5/10 to 9/10. Same model (Sonnet 4.6). Just better scaffolding.

Full methodology: UpCommander Benchmark Blog Post | Benchmark data: evaluations/


Quickstart

Prerequisites

  • Node.js 18+
  • npx tsx available (npm install -g tsx or use npx tsx directly)
  • Anthropic API key

BYOK Setup

export ANTHROPIC_API_KEY=sk-ant-...

Or save it permanently:

mkdir -p ~/.claude-commander
echo '{"apiKeys":{"anthropic":"sk-ant-..."}}' > ~/.claude-commander/config.json

Run a task

# Generate contract + execute K2 worker (Sonnet 4.6)
npx tsx src/cli.ts run "add pagination to the notes API"

# Same + V2O quality review with Opus after
npx tsx src/cli.ts run "add pagination to the notes API" --quality

# Generate CONTRACT.md only (to review before running)
npx tsx src/cli.ts contract "add pagination to the notes API"

# Regenerate the codebase index
npx tsx src/cli.ts index

# Quality review on specific files
npx tsx src/cli.ts review src/app/api/notes/route.ts

Architecture

┌─────────────────────────────────────────────────────────┐
│                      cli.ts                              │
│   run | contract | index | review                       │
└───────────────────────┬─────────────────────────────────┘
                        │
          ┌─────────────▼──────────────┐
          │   index-connector/         │  ← reads .codebase-index/
          │   loadIndexContext(L0/L1)  │    L0=2K tokens, L1=8K tokens
          │   buildSystemPrompt()      │    91% compression vs raw files
          └─────────────┬──────────────┘
                        │
          ┌─────────────▼──────────────┐
          │   workers/recipe-runner.ts │  ← assembles system prompt
          │   runRecipe(K2_SOLO)       │    then calls ApiAgent
          └─────────────┬──────────────┘
                        │
          ┌─────────────▼──────────────┐
          │   api-agent.ts             │  ← multi-provider HTTP client
          │   Anthropic / OpenAI /     │    with streaming + retry
          │   Google / OpenRouter      │
          └────────────────────────────┘

Optional quality pass:
          ┌──────────────────────────────┐
          │   quality-review/            │  ← V2O: Opus one-shot review
          │   reviewFiles()              │    NO retry loop
          └──────────────────────────────┘

Optional orchestration:
          ┌──────────────────────────────┐
          │   ephemeral/                 │  ← Haiku orchestrator (-96% cost)
          │   startEphemeralTurn()       │    for multi-session workflows
          └──────────────────────────────┘

Key modules

| Module | Purpose | Token cost | |--------|---------|-----------| | index-connector/ | L0/L1/L2 codebase index reader | L0=~2K, L1=~8K | | workers/k2-solo.ts | Default strategy: Sonnet + CONTRACT + L1 index | ~0.08/run | | workers/pipeline-3tier.ts | High-stakes: Opus contract → DeepSeek impl → Sonnet review | ~5× K2 | | quality-review/ | V2O one-shot Opus review (no retry) | ~$0.15-0.50 | | ephemeral/ | Haiku orchestrator, $0.0077/turn vs $0.20 Sonnet | -96% orch cost | | orchestrator.ts | Hot-reloadable routing rules (routing-rules.json) | — | | ast-summary/ | SHA-cached tree-sitter file summaries | -91% per-file tokens |


What NOT to do

These are the most common mistakes — all empirically validated as harmful:

1. Agent Teams (parallel workers) 73–124% more expensive than sequential. Every agent loads the full codebase context independently. Three agents = three copies of your 21K-token CLAUDE.md. Never use unless wall-clock time has direct dollar value.

2. Retry loops (self-evolution) When a model retries, it doesn't make surgical edits. It regenerates entire files. Fixing a broken import path means rewriting the whole route file — and losing all the CRUD endpoints that were correct the first time. Proved across 15 retry attempts in 3 runs. Quality degraded from 9/10 → 6/10 on retries. Use a one-shot Opus quality review instead.

3. Skipping the contract on multi-file tasks For any task touching 3+ files, the CONTRACT.md costs ~$0.15 to generate and saves 47–54% on the task cost. Paid back on the first run, every time.


Routing Logic

routing-rules.json controls which strategy runs for which task type. Hot-reloaded without app restart.

{
  "default_strategy": "k2",
  "routing_rules": [
    { "condition": "task.file_count >= 3 && task.is_greenfield", "strategy": "k2" },
    { "condition": "task.type === 'high_stakes'", "strategy": "pipeline" }
  ]
}

Strategies

| Strategy | When | Cost | |----------|------|------| | k2 | Default — 1-5 files, cost-optimal | ~$0.08/run | | pipeline | High-stakes, >$0.50 estimated | ~5× K2 | | sonnet_raw | Single-file trivial fixes only | baseline | | opus_raw | Architecture review, no scaffolding | expensive |


Adding Worker Recipes

Drop a new file in workers/ and reference it in routing-rules.json:

// workers/my-recipe.ts
import type { WorkerRecipe } from './types';

export const MY_RECIPE: WorkerRecipe = {
  name: 'my-recipe',
  role: 'solo',
  model: 'claude-sonnet-4-6',
  system_prompt_parts: [
    { type: 'karpathy' },
    { type: 'index', level: 'L1' },
    { type: 'contract', path: 'CONTRACT.md' },
    { type: 'raw', content: 'Additional instructions...' },
  ],
  index_level: 'L1',
  max_tokens: 8192,
  budget_usd: 0.30,
};

Programmatic API

import {
  loadIndexContext,
  buildSystemPrompt,
  reviewFiles,
  runRecipe,
  K2_SOLO_WORKER,
} from 'upcommander';

// Load codebase context
const ctx = loadIndexContext('/path/to/repo', 'L1');
console.log(`${ctx.tokenEstimate} tokens`);

// Run a task
const result = await runRecipe(K2_SOLO_WORKER, 'add pagination to notes API', '/path/to/repo', {
  contractPath: '.claude-coord/CONTRACT.md',
  streamChunk: chunk => process.stdout.write(chunk),
});

// Quality review
const review = await reviewFiles({
  contractPath: '.claude-coord/CONTRACT.md',
  files: ['src/app/api/notes/route.ts'],
  repoPath: '/path/to/repo',
});
console.log(`Score: ${review.overallScore}/10`);

Cost Benchmarks (N=52+ runs)

All results on Sonnet 4.6 against a production Next.js/TypeScript/Supabase codebase. Your numbers will differ — the directions hold, the magnitudes are setup-specific.

| Condition | ACs met | Quality | Cost | |-----------|---------|---------|------| | V1: Vague brief | 2/5 | 5/10 | $0.91 | | V2: CONTRACT.md | 3.3/5 | 9.8/10 | $0.83 | | NS: CONTRACT + retry loop | 4/5 | 6/10 | $1.40 | | V2O: CONTRACT + Opus review | 4/5 | 9.8/10 | $1.30 |

Key findings:

  • Retry loops degrade quality (9→6/10). Model regenerates whole files while fixing one issue.
  • V2O adds zero quality at +56% cost (clean N=5 retest, full file context). When the CONTRACT is well-formed, V2 alone reaches 9.8/10 — nothing for Opus to fix.
  • V2 (CONTRACT only) is the optimal strategy. Don't add a review pass. Write a better brief instead.

Research Foundations


What's Coming

VS Code extension — UpCommander is being built into a free VS Code extension that runs this entire stack inside your editor. No shell scripts, no tsx, no context switching. Contract generation, worker dispatch, cost tracking, and quality review triggered directly from the command palette or a sidebar panel.

Multi-model routing — Route cheap models (DeepSeek, Haiku) to boilerplate and expensive models (Opus, GPT-4o) only to design decisions. Early benchmarks show another 30–40% cost reduction on top of the stacked savings above.

UpLink desktop — Full session management, mobile bridge, and persistent cost tracking across sessions. Wraps UpCommander with a GUI for teams who want visibility without the terminal.

⭐ Star this repo to get notified when the VS Code extension ships. That's where most developers will want to run this.


License

MIT — open-source, BYOK, no telemetry.

Built by UpGPT. Questions: [email protected]