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

@uzysjung/agent-harness

v26.97.0

Published

Curate vetted AI-coding skills & plugins by your tech stack — install only what you need, across Claude Code, Codex, OpenCode & Antigravity

Downloads

2,144

Readme

uzys-agent-harness

Install only the AI-coding skills & plugins your tech stack actually needs — vetted, curated, and set up with one command across Claude Code, Codex, OpenCode & Antigravity.

Coding agents keep getting stronger out of the box — piling on skills and MCPs you'll never use just bloats their context. And the awesome-lists have too many options to wade through. agent-harness curates by tech stack: of the vetted options, you install only what this project actually calls for. Claude Code is first-class; Codex / OpenCode / Antigravity get the skills + rules layer. Project scope by default — no global pollution unless you ask.

License Version CI

agent-harness demo — one-command install of vetted AI-coding skills & plugins

What "vetted" means — ≥ 1000 GitHub stars + active maintenance + a Docker install-verification run (49/59 assets green today), re-checked monthly by a CI cron (catalog-verify, trust-tier-drift). It is not a line-by-line security audit or a prompt-injection scan of asset contents. npm/npx assets are version-pinned; plugin/skill assets resolve to upstream HEAD (not commit-pinned yet). Treat installed assets like any third-party dependency — see SECURITY.md.

🇰🇷 한국어


Install

npx -y @uzysjung/agent-harness

A 6-step interactive wizard guides everything. No flags needed. Safe on an existing project — it backs up your settings.json / CLAUDE.md before any change (details below); nothing is deleted.

Step 1/6  Tracks            ← pick your stack
Step 2/6  CLI               ← claude / codex / opencode / antigravity
Step 3/6  Install items     ← review pre-checked recommendations
Step 4/6  Scope             ← Project (default) or Global
Step 5/6  Confirm
Step 6/6  Installing

After install:

claude    # launch your CLI — installed skills, rules, and hooks are now active

Non-interactive install (CI / scripts / Docker)

The wizard needs a TTY. For CI pipelines, onboarding scripts, or containers, use flags — the same path our own verification CI runs on:

npx -y @uzysjung/agent-harness install \
  --track tooling --cli claude --scope project \
  --with bmad-method

| Flag | Meaning | |------|---------| | --track <name> | Track to install (repeatable) | | --cli <target> | claude / codex / opencode / antigravity (repeatable) | | --scope <s> | project (default) or global | | --with <asset-id> / --without <asset-id> | Add / remove any catalog asset by id (repeatable) — ids in the compatibility matrix |

v26.81.0 (ADR-022): per-asset flags like --with-bmad were removed — --with <asset-id> is the single opt-in surface. Behavior flags (--with-karpathy-hook, --with-codex-trust, --with-prune, …) remain.

What a track actually installs (example)

Curation, not a list to browse — pick csr-supabase and step 3 pre-checks exactly these, nothing else (uncheck any before install):

| Track | Pre-checked assets | |---|---| | csr-supabase | react-best-practices · shadcn-ui · web-design-guidelines · supabase-agent-skills · postgres-best-practices · supabase-cli | | data | polars · dask · python-resource-management · python-performance-optimization · anthropic-data-plugin |

Full per-track matrix ↓ · or the compatibility matrix.


Installing into an existing project

agent-harness never silently overwrites your config. Before replacing an editable file whose contents differ, it writes a timestamped backup next to it — and every backup path is printed in the install summary (backup rows). Nothing is deleted.

| You already have… | What happens | |---|---| | .claude/settings.json with your own hooks / statusLine | Backed up to settings.json.backup-<ts> before update | | Root CLAUDE.md (yours differs from the generated one) | Backed up to CLAUDE.md.backup-<ts> before the merge write | | .claude/ on --reinstall / update mode | The whole directory is renamed to .claude.backup-<ts> first | | .mcp.json | Your existing MCP servers are preserved and merged, not replaced |

Fresh project? None of this triggers — backups only protect pre-existing files.


Tracks

A track is a preset bundle for your stack. Pick one or more at step 1; each track determines which skills/plugins/rules are pre-checked in step 3.

Dev tracks

| Track | Stack | |---|---| | csr-supabase | Vite + React + Supabase | | csr-fastify | Vite + React + Fastify | | csr-fastapi | Vite + React + FastAPI | | ssr-nextjs | Next.js (App Router) | | ssr-htmx | HTMX + server-side | | data | DuckDB + Polars + PySide6 | | full | union of all dev tracks |

Business tracks

| Track | Use | |---|---| | executive | proposals, due diligence, decks, financial models | | project-management | PM workflow + reviews | | growth-marketing | growth + content marketing |

Meta

| Track | Use | |---|---| | tooling | Bash + Markdown meta-projects (no app stack) |


What gets installed per track

External assets are recommended automatically based on your track selection. Step 3 shows them pre-checked; you can toggle anything before install.

Frontend (csr-* / ssr-nextjs / full)

| Asset | What | Source | |---|---|---| | react-best-practices | React patterns and component guidelines | LokeshSakthivel | | shadcn-ui | Radix-based component copy + Tailwind theme | shadcn (official) | | web-design-guidelines | UX/UI best practices | LokeshSakthivel | | impeccable | UI design, critique, and visual review skills | pbakaus |

Backend (csr-* / ssr-* / full)

| Asset | What | Source | |---|---|---| | railway-skills | Railway deploy + project/service/env management | Railway official | | supabase-agent-skills (csr-supabase) | Supabase agent skills | Supabase official | | postgres-best-practices (csr-supabase) | Postgres patterns | Supabase official | | supabase-cli (csr-supabase) | Supabase CLI (supabase login for OAuth) | npm | | vercel-cli (csr-supabase) | Vercel CLI | npm | | netlify-cli (csr-supabase) | Netlify CLI | npm |

Data (data / full)

| Asset | What | Source | |---|---|---| | polars-K-Dense | Polars — fast Rust DataFrame (pandas alternative) | K-Dense-AI | | dask-K-Dense | Dask — distributed processing | K-Dense-AI | | python-resource-management | Memory / CPU management patterns | wshobson | | python-performance-optimization | Profiling + vectorization | wshobson | | anthropic-data-plugin | Visualization + SQL exploration | Anthropic official |

Business (executive / project-management / growth-marketing)

| Asset | What | Source | Tracks | |---|---|---|---| | anthropic-document-skills | pptx / docx / xlsx / pdf authoring | Anthropic | executive · full | | c-level-skills | 28 advisory skills (CEO/CFO/COO) | claude-code-skills | executive · full | | business-growth-skills | Growth, finance, marketing playbooks | claude-code-skills | executive · full · growth-marketing | | finance-skills | Financial models | claude-code-skills | executive · full | | pm-skills | PM workflows | claude-code-skills | project-management | | product-skills | Product discovery + delivery | claude-code-skills | dev + PM | | marketing-skills / content-creator / demand-gen / research-summarizer | Marketing playbooks | claude-code-skills | growth-marketing |

Dev Tools (all dev tracks)

| Asset | What | Source | |---|---|---| | playwright-skill | E2E test authoring with Playwright | testdino-hq | | find-skills | Search and rank installed skills | vercel-labs | | agent-browser | Browser automation CLI for agents | npm | | architecture-decision-record | ADR authoring | yonatangross | | karpathy-coder | Pre-commit quality gate hook | claude-code-skills | | product-skills | Product engineering | claude-code-skills | | multi-persona-review ★ | Critique one artifact via 3-5 parallel personas → P0/P1/P2 fixes | this project (core) | | gap-analysis-e2e ★ | Detect north-star / correctness / UX gaps, then benchmark how reference services solved each | this project (core) | | ultracode-service-audit ★ | Multi-agent, adversarially-verified full-service audit (7 dimensions) → milestone roadmap | this project (core) |

dev-method skills — first-party (official) workflow methodology bundled with the harness. Core on every dev track (installed by default; uncheck at step 3 or --without <id> to skip). Repo-bundled templates — no external download. Installs across all 4 CLIs: Claude (.claude/skills/) and Codex / Antigravity as native skills (.agents/skills/<id>/SKILL.md), plus OpenCode as a command fallback (.opencode/commands/<id>.md, since OpenCode has no native skill concept).

Workflow (opt-in — pick one or more at step 3)

Which one? See the Workflow curation guide — a vetted comparison of all 6 installable workflows (plus honest pointers to Spec Kit / Kiro, which we recommend but don't auto-install).

| Asset | What | Activates | |---|---|---| | superpowers | Agentic skills framework, Anthropic official marketplace | obra/superpowers | | ecc-plugin | 60 agents · 230 skills · 75 commands | affaan-m | | openspec | Spec-driven brownfield delta workflow (propose → apply → archive) | Fission-AI | | bmad-method | Multi-agent agile workflow (PM/Architect/Dev, 12+ agents) | bmad-code-org | | addy-agent-skills | /spec /plan /build /test /review /ship /code-simplify skills | addyosmani's workflow | | wshobson-agents | Multi-agent orchestration workflows (full-stack/tdd/review), cross-CLI | wshobson |

First-party dev-method skills (official, core on every dev track — installed by default, uncheck at step 3 or --without <id> to skip; repo-bundled templates; install across all 4 CLIs — Claude + Codex/Antigravity native skills + OpenCode command fallback):

| Asset | What | Source | |---|---|---| | asis-tobe-decision ★ | Present an A-or-B / approval moment as context → recommendation → option table → AS-IS/TO-BE contrast | this project (core) | | compaction-handoff ★ | Persist durable state + git snapshot + resume anchor before a context /compact | this project (core) | | northstar-roadmap ★ | Measure current state vs the vision doc → ranked feature backlog persisted to docs/plans + memory | this project (core) |

First-party advisor (official, opt-in--with gemini-consult; repo-bundled, installs across all 4 CLIs; needs the external Antigravity agy CLI at runtime):

| Asset | What | Source | |---|---|---| | gemini-consult | Consult Gemini (via agy) for natural Korean phrasing + multi-persona second-opinion review — an idiomatic, independent second model | this project |

Security & ECC (opt-in)

| Asset | What | Source | |---|---|---| | trailofbits-skills | Differential security review | Trail of Bits | | ecc-plugin | ECC plugin (project-scoped via prune-ecc.sh) | affaan-m | | ecc-prune | Trim ECC down to a curated set (4 agents + 8 skills + 3 commands) | this project |


Trust tiers

Every external asset carries a trust tier, shown as a badge in step 3:

  • ★ official — Anthropic-official marketplaces + this harness's own assets.
  • vetted — community assets with ≥ 1000 GitHub stars and active maintenance. Pre-checked when they match your track.
  • ⚠ experimental — under 1000 stars. Opt-in only (not pre-checked), listed at the bottom of each category.

Tiers inform, never block — you always review and choose what installs. Recommended assets (official/vetted matching your track) sort to the top.

How is "verified" backed up? See the Compatibility & verification matrix — install methods are checked against real registries/marketplaces, and the core workflow set is verified by real install in an isolated Docker container (not a static table). Trust tiers are auto-monitored for star-drift monthly.


Scope

Step 4 asks where the install writes.

| | Project (default) | Global (opt-in) | |---|---|---| | claude plugin | --scope project (entries isolated by projectPath in installed_plugins.json) | --scope user | | npx skills | project node_modules | -g (user-level) | | npm | --save-dev (devDependency) | -g | | Codex (prompts / skills / config) | .codex/ in your project | ~/.codex/ | | Antigravity (skills / workflows) | .agents/ in your project | ~/.gemini/antigravity/ | | ~/.claude/skills/ · ~/.codex/ · ~/.opencode/ · ~/.gemini/ · npm root -g | not touched | written per asset |

Project scope keeps the install confined to your repo. Other projects on the same machine are unaffected.

Claude CLI itself writes plugin cache under ~/.claude/plugins/cache/ regardless of scope — but the metadata in installed_plugins.json isolates entries by projectPath, so other projects don't see them.


Uninstall

npx -y @uzysjung/agent-harness uninstall

Reads .claude/.harness-install.json (created during install) and reverses what was installed.

  • Project-scope assets: removed automatically (claude plugin uninstall --scope project, npm uninstall --save-dev, .codex/ cleanup, etc.).
  • Project root CLAUDE.md: removed only if it still matches the installed version (sha256); kept with a notice if you've edited it since install.
  • Global-scope assets: listed as advisory only — you remove them yourself. Uninstall never touches another project or your global config without explicit action.

Flags:

| Flag | What | |---|---| | --dry-run | List reverse steps, change nothing | | --keep-templates | Remove external assets but keep .claude/, .codex/, .opencode/ |


How it works

┌──────────────────────────────────────────────────────────┐
│  npx -y @uzysjung/agent-harness                         │
│         │                                                │
│         ▼                                                │
│  ┌─ 6-step wizard ──────────────────────────────────┐    │
│  │  Track(s) → CLI(s) → Items → Scope → Confirm    │    │
│  └──────────────────┬───────────────────────────────┘    │
│                     ▼                                    │
│  ┌─ Phase 1: Templates ─────────────────────────────┐    │
│  │  .claude/{rules,agents,hooks,commands,skills}    │    │
│  │  CLAUDE.md (scaffold) · .mcp.json                │    │
│  └──────────────────┬───────────────────────────────┘    │
│                     ▼                                    │
│  ┌─ Phase 2: External assets ───────────────────────┐    │
│  │  claude plugin / npx skills / npm / shell-script │    │
│  │  Honors the scope chosen at step 4               │    │
│  └──────────────────┬───────────────────────────────┘    │
│                     ▼                                    │
│  ┌─ Phase 3: install log ───────────────────────────┐    │
│  │  .claude/.harness-install.json                   │    │
│  │  (drives `uninstall`)                            │    │
│  └──────────────────────────────────────────────────┘    │
└──────────────────────────────────────────────────────────┘

After install, a tooling + Claude project looks like:

your-project/
├── .claude/
│   ├── rules/          # coding conventions for your stack
│   ├── agents/         # subagent definitions
│   ├── hooks/          # lifecycle / pre-commit hooks
│   └── settings.json   # your existing one is backed up first
├── CLAUDE.md           # fill-in scaffold (yours backed up if it differed)
└── .mcp.json           # MCP servers, merged with yours

CLI support

| CLI | Status | |---|---| | Claude Code | First class — all assets and hooks | | Codex (OpenAI) | Skills + AGENTS.md rules for your stack | | OpenCode | Skills + AGENTS.md integration | | Antigravity (Google) | Project: .agents/rules/ (context, always) + .agents/skills/ (dev-method skills) |

Pick one or more at step 2.


Advanced


License

MIT.