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

codex-plugin

v0.1.3

Published

CLI for installing a remote Codex plugin marketplace into project or global configuration.

Vulnerabilities

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

Links

Git

Maintainers

grabbougrabbouthymikeethymikee

Keywords

Readme

codex-plugin

CLI for installing a remote Codex plugin marketplace from a GitHub repository into either project or global configuration.

It clones the remote repository, reads .agents/plugins/marketplace.json, copies plugin directories into .codex/plugins/, and writes marketplace entries that point to ./.codex/plugins/<plugin-name>.

Expected repository structure:

  • .agents/plugins/marketplace.json is the source marketplace file committed to the repo
  • plugins/<plugin-name> contains each plugin directory

In the repo marketplace, source.path values should be relative to the repo root:

  • ./plugins/building-react-native-apps
  • ./plugins/testing-react-native-apps

During installation, the CLI rewrites those entries to the installed layout under .codex/plugins/.

It supports one command today:

  • codex-plugin add <org/repo>

Install targets:

  • personal Codex marketplace under ~/.agents/plugins/marketplace.json
  • project Codex marketplace under <cwd>/.agents/plugins/marketplace.json

Install layout:

  • global: marketplace in ~/.agents/plugins/marketplace.json, plugins copied into ~/.codex/plugins/
  • project: marketplace in <cwd>/.agents/plugins/marketplace.json, plugins copied into <cwd>/.codex/plugins/

Run with:

bun run src/index.ts add callstackincubator/agent-skills

Flags:

bun run src/index.ts add callstackincubator/agent-skills --project
bun run src/index.ts add callstackincubator/agent-skills --global
bun run src/index.ts add callstackincubator/agent-skills --ref feat/codex-plugin
bun run src/index.ts add callstackincubator/agent-skills --project --yes

Intended published usage:

npx codex-plugin add callstackincubator/agent-skills
npx codex-plugin add callstackincubator/agent-skills --ref feat/codex-plugin