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

aos-harness

v0.9.0

Published

Agentic Orchestration System — assemble AI agents into deliberation and execution teams

Readme

aos-harness

Agentic Orchestration System — Assemble specialized AI agents into deliberation and execution teams.

Breaking change in 0.6.0: aos-harness no longer bundles adapter code. You must install the adapter(s) for the AI CLI(s) you want to use as separate packages. If you upgrade from 0.5.x and run aos run without the matching @aos-harness/<name>-adapter installed, the CLI will print an install hint and exit. See CHANGELOG for the full migration note.

Prerequisites

Getting Started

1. Install the CLI

bun add -g aos-harness
# or: npm i -g aos-harness

Or install it into the current project:

bun add aos-harness
# or: npm install aos-harness

2. Install an adapter

Install the vendor CLI you want to drive first, then install the matching AOS adapter package. The adapter is the AOS integration layer on top of the vendor CLI:

  • claude + @aos-harness/claude-code-adapter
  • codex + @aos-harness/codex-adapter
  • gemini + @aos-harness/gemini-adapter
  • pi + @aos-harness/pi-adapter

Pick the AI CLI you'll drive agents with and install the matching adapter. You can install more than one. Versions are lockstep — pin the adapter to the same version as the CLI.

bun add -g @aos-harness/claude-code-adapter   # Anthropic's Claude Code
bun add -g @aos-harness/gemini-adapter         # Google's Gemini CLI
bun add -g @aos-harness/codex-adapter          # OpenAI's Codex CLI
bun add -g @aos-harness/pi-adapter             # Pi (https://pi.dev)

Project-local adapter install also works:

bun add @aos-harness/codex-adapter
# or: npm install @aos-harness/codex-adapter

3. Initialize and run

# Initialize a project (writes .aos/ and copies core/ into the project)
aos init
# local install via Bun
bunx aos init
# local install via npm
npx aos init

# Or scan only in CI / automation
aos init --non-interactive

# Or install missing adapter packages after config generation
aos init --apply

# Run a strategic deliberation
aos run strategic-council --brief brief.md

# Run a CTO execution workflow
aos run cto-execution --brief feature-brief.md --domain saas

# List available agents, profiles, and domains
aos list

# Create custom configs
aos create agent my-analyst
aos create profile my-review

# Validate all configurations
aos validate

Adapter Model Selection

aos run resolves model settings in this order:

  1. adapter-scoped settings in .aos/config.yaml adapter_defaults
  2. legacy .aos/adapter.yaml
  3. AOS_MODEL_ECONOMY / AOS_MODEL_STANDARD / AOS_MODEL_PREMIUM
  4. adapter defaults

Default behavior:

  • pi pins explicit tier models by default
  • codex, claude-code, and gemini let the vendor CLI choose its default model unless you set explicit tier models

Example:

api_version: aos/config/v2
adapters:
  enabled: [codex, pi]
  default: codex
adapter_defaults:
  codex:
    use_vendor_default_model: true
  pi:
    use_vendor_default_model: false
    models:
      economy: anthropic/claude-haiku-4-5
      standard: anthropic/claude-sonnet-4-6
      premium: anthropic/claude-opus-4-7

Claude Code note:

  • aos init now checks claude auth status --json.
  • If Claude Code is being forced through ANTHROPIC_API_KEY, the readiness scan will tell you. If sessions fail with Invalid API key, unset or refresh that key, or switch back to claude login auth.

Exit Codes

| Code | Meaning | |---|---| | 0 | Success | | 1 | Uncaught runtime error | | 2 | Invalid input (unknown adapter, bad path, bad URL, missing adapter package) | | 3 | Validation failure that requires user action (aos init --non-interactive --adapter ... selected adapter not ready, or profile tool-policy widening failure) |

What It Does

AOS Harness orchestrates multiple AI agents with distinct cognitive biases into structured deliberation and execution sessions:

  • Deliberation — Agents debate a strategic question. An Arbiter synthesizes ranked recommendations with documented dissent.
  • Execution — A CTO orchestrator delegates production work through multi-phase workflows with review gates.

Ships with 13 agent personas, 6 orchestration profiles, 5 domain packs, and full constraint management (time, budget, rounds).

Documentation

License

MIT