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

@topy-ai/cofounders

v0.1.1

Published

Your team of AI cofounders from TOPY.AI in every coding agent: install the team (user scope), bind a repo to its topy.ai project, and keep the project's topy-memory.

Readme

@topy-ai/cofounders

Your team of AI cofounders from TOPY.AI in every coding agent: one MCP server (https://topy.ai/mcp/team), one sign-in, the cofounders you choose — Elon (CEO), Munger (CFO), Deming (COO), Diffie (CSO), Turing (CTO), Jony (CPO), Ziglar (CRO) and Maggie (CMO, on cmo.so with its own plan).

npx @topy-ai/cofounders install --members all   # every project (user scope): Claude Code, Codex and the skills
cd my-project && npx @topy-ai/cofounders init   # this repo: bind it to its topy.ai project

Two levels, like the dashboard

| | Saved on topy.ai | In your clients | |---|---|---| | Your default team (install, Founder Profile → My AI team) | the account's team | topy-cofounders → https://topy.ai/mcp/team in Claude Code (--scope user) and Codex | | A project (init, the project's AI team) | the project, and its own team if you give it one | .mcp.json → the same URL with an X-Topy-Project: <id> header: in that folder every call defaults to the project, and the one sign-in still counts |

init finds the project by its website (from .maggie/project.json, the Astro or Next config, package.json homepage or CNAME; or --website), or asks the AI CEO to create it from the website. It writes:

  • .topy/project.json — the project id, name, website and server URL (no secrets; commit it);
  • .mcp.json — the project's topy-cofounders entry (same URL, the project in a header), next to your other servers;
  • a block in CLAUDE.md / AGENTS.md — the project and the topy-memory instructions for your agents;
  • .topy/memory.md — the project's memory.

topy-memory

What the cofounders remember about one project — the founder's preferences, the project's conventions, lessons from fixed mistakes and the error history — lives on topy.ai, so Claude, Codex, claude.ai and the scheduled Routines read the same memory. .topy/memory.md is the repo's generated copy.

cofounders memory add --kind convention --rule "Deploy only through CI." --roles cto --evidence .github/workflows/deploy.yml
cofounders memory list --candidates
cofounders memory confirm <id>
cofounders memory error --fingerprint ci-node-version --message "…" --fixed --resolution "…" --validation "…"
cofounders memory pull

A new item is a candidate until you confirm it; only active items reach the cofounders. Keys, tokens and passwords are refused. In an agent, the same tools are memory_context, memory_remember, memory_review and memory_record_error.

Sign-in

cofounders login (the device flow, shared with the role CLIs: ~/.config/topy/credentials.json) or TOPY_API_KEY. Each agent signs in to the MCP server itself: in Claude Code /mcp → topy-cofounders → Authenticate.