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

@every-env/compound-plugin

v0.1.1

Published

A Claude Code plugin marketplace featuring the **Compound Engineering Plugin** — tools that make each unit of engineering work easier than the last.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

kieranklaassenkieranklaassendannyazizdannyazizyash_poojaryyash_poojarydanshipperdanshipper

Keywords

Readme

Compound Marketplace

A Claude Code plugin marketplace featuring the Compound Engineering Plugin — tools that make each unit of engineering work easier than the last.

Claude Code Install

/plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin
/plugin install compound-engineering

OpenCode + Codex (experimental) Install

This repo includes a Bun/TypeScript CLI that converts Claude Code plugins to OpenCode and Codex.

# convert the compound-engineering plugin into OpenCode format
bunx @every-env/compound-plugin install compound-engineering --to opencode

# convert to Codex format
bunx @every-env/compound-plugin install compound-engineering --to codex

Local dev:

bun run src/index.ts install ./plugins/compound-engineering --to opencode

OpenCode output is written to ~/.opencode by default, with opencode.json at the root and agents/, skills/, and plugins/ alongside it. Both provider targets are experimental and may change as the formats evolve. Codex output is written to ~/.codex/prompts and ~/.codex/skills, with each Claude command converted into both a prompt and a skill (the prompt instructs Codex to load the corresponding skill). Generated Codex skill descriptions are truncated to 1024 characters (Codex limit).

Workflow

Plan → Work → Review → Compound → Repeat

| Command | Purpose | |---------|---------| | /workflows:plan | Turn feature ideas into detailed implementation plans | | /workflows:work | Execute plans with worktrees and task tracking | | /workflows:review | Multi-agent code review before merging | | /workflows:compound | Document learnings to make future work easier |

Each cycle compounds: plans inform future plans, reviews catch more issues, patterns get documented.

Philosophy

Each unit of engineering work should make subsequent units easier—not harder.

Traditional development accumulates technical debt. Every feature adds complexity. The codebase becomes harder to work with over time.

Compound engineering inverts this. 80% is in planning and review, 20% is in execution:

  • Plan thoroughly before writing code
  • Review to catch issues and capture learnings
  • Codify knowledge so it's reusable
  • Keep quality high so future changes are easy

Learn More