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

agenture-cli

v0.1.10

Published

Bootstrap .agents/ hub, project memory, and tool snippets (Cursor, Claude Code, Copilot); skills via npx skills / skills.sh.

Downloads

618

Readme

agenture-cli

agenture-cli

Bootstrap your repo with a shared memory system, agent rules, and skill install playbooks — compatible with Claude Code, GitHub Copilot, Cursor, and OpenAI Codex.

What it does

Phase 1 — init: copies a fixed set of files into your project (no prompts, no network):

| What | Where | |---|---| | Shared memory system | .memory/ + AGENT_MEMORY_RULES.md | | Agent hub | .agents/ (skills land here for most tools) | | Universal agent instructions | AGENTS.md | | Skills install playbook | AGENT_SKILLS_INSTALL.md | | Claude Code | CLAUDE.md + .claude/commands/setup-agenture.md | | GitHub Copilot | .github/copilot-instructions.md | | Cursor | .cursor/rules/agent-memory.mdc |

Phase 2 — skills: your agent reads the repo, searches skills.sh, and installs the skills that match your stack via npx skills.

Requirements

  • Node.js 20+

Usage

On any existing project

cd /path/to/your/project
npx agenture-cli@latest init

Existing files are left untouched. Use --force to replace them:

npx agenture-cli@latest init --force

From a clone of this repo

pnpm install
pnpm run build
node dist/cli.js init /path/to/your/project

Check your environment

npx agenture-cli@latest doctor

Prints your Node/npx versions and skills CLI pointers.

Phase 2: install skills

After init, the CLI prints a prompt to paste into your agent. It will:

  1. Scan your stack (package.json, lockfiles, frameworks, etc.)
  2. Search skills.sh with npx skills find
  3. Install the relevant skills with npx skills add … -a <agent>

Claude Code — run the slash command:

/setup-agenture

Copilot / Cursor / Codex / other agents — paste the prompt printed by init, or tell your agent:

Read AGENT_SKILLS_INSTALL.md at the repo root and execute phase 2 — real npx skills commands, use the right -a for your agent (github-copilot, cursor, codex…).

Skills are installed into .agents/skills/ (project-scoped) by default. Commit that folder to share them with your team.

Memory system

Every agent that reads the bootstrapped files follows the same memory discipline defined in AGENT_MEMORY_RULES.md:

  • Decisions, preferences, conventions, and patterns go into .memory/{category}/YYYY-MM-DD-slug.md
  • The agent updates .memory/INDEX.md after each write
  • No keyword needed — any lasting project signal triggers a write automatically

Categories: decision/, preference/, context/, pattern/

Telemetry

The skills CLI (npx skills) collects usage telemetry by default. Opt out:

export DISABLE_TELEMETRY=1
# or
export DO_NOT_TRACK=1

License

MIT