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

@miranda0808/maya-codex

v0.1.4

Published

Install the repo-local Maya runtime into the current project or a target directory.

Vulnerabilities

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

Links

Maintainers

miranda0808miranda0808

Keywords

Readme

@miranda0808/maya-codex

Install the repo-local Maya runtime into the current project or a target directory.

Usage

npx @miranda0808/maya-codex init
npx @miranda0808/maya-codex init --dry-run
npx @miranda0808/maya-codex init --force
npx @miranda0808/maya-codex init --target ../some-project

What It Installs

  • portable AGENTS.md
  • .env.example
  • .gitignore entries for .env and .env.local
  • commands/ compatibility docs
  • .maya/
  • templates/
  • campaigns/README.md
  • research/README.md
  • tools/
  • .agents/skills/ bootstrap entry skills for /maya-consult, /maya-task, and /product
  • .agents/skills/ marketing specialist skills used by the Codex specialist subagents
  • .codex/config.toml
  • .codex/agents/

Specialist Runtime

After bootstrap, the Codex marketing specialist subagents in .codex/agents/ load and follow their matching repo-local skills from .agents/skills/<specialist>/SKILL.md. The TOMLs stay as Codex-facing wrappers, while the matching skill remains the primary workflow contract for each marketing specialist.

Secrets

After install, copy .env.example to .env or .env.local in the target repo.

  • .env.local overrides .env when both exist.
  • Maya keeps .env and .env.local out of git by adding them to .gitignore.
  • The Meta boundary auto-loads META_ACCESS_TOKEN and META_AD_ACCOUNT_ID from those files for each invocation.

Options

  • --dry-run prints the planned writes without modifying the target project.
  • --force overwrites files Maya previously installed.
  • --target <path> installs into a different existing directory.

Codex Entry Skills

After install, Codex App should surface these repo-local Maya entrypoints from .agents/skills/:

  • /maya-consult
  • /maya-task
  • /product