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

@agentproto/apps

v0.8.0

Published

@agentproto/apps — a home for ready-made agentproto apps (teams of agents + their workflows), declared with @agentproto/app-kit. Import a team (code-team, content-team, …) and use any of its agents/workflows from your own host: in-process via toMastraAgen

Readme

@agentproto/apps

Ready-made agentproto appsteams of agents plus the workflows they run, each declared with @agentproto/app-kit. Import a team, use any subset of its agents/workflows from your own host.

import { codeTeam } from "@agentproto/apps/code-team"

// In-process: build the team and pick the agent(s) you want.
const built = await codeTeam.toMastraAgents({ resolveModel: (ref) => registry.resolve(ref) })
built["@agentproto/reviewer"].agent   // just the reviewer, as a runnable Mastra agent

// …or use several. The record is keyed by agent id.
const { ["@agentproto/implementer"]: impl, ["@agentproto/fixer"]: fixer } = built

An app here is a plain AppHandlecodeTeam.agents, codeTeam.workflows, codeTeam.toMastraAgents(...), codeTeam.emit(dir). Nothing new to learn.

Teams

| Team | Import | Agents | Workflows | | --- | --- | --- | --- | | code-team | @agentproto/apps/code-team | implementerreviewerfixer | deliver-change | | content-team | @agentproto/apps/content-team | researcherwritereditorillustrator | produce-content, produce-cover | | mail-triage | @agentproto/apps/mail-triage | triager | triage-inbox | | media-viewer | @agentproto/apps/media-viewer | cataloger | scan-media | | session-viewer | @agentproto/apps/session-viewer | narrator | narrate-session |

Each team is a folder with agents/<name>.ts (one self-contained file per agent — its defineAgent handle + body) and workflows/<name>.ts, composed in the team's index.ts. A new team is a sibling folder + a re-export.

Two ways to consume

  • In-processawait team.toMastraAgents({ resolveModel }) returns the built agents keyed by id; take the ones you need. @mastra/core is a peer dependency, so install it in the host.
  • On diskawait team.emit(dir) writes the AGENT.md / WORKFLOW.md manifests for a runtime that loads a workspace from disk. No Mastra needed.

Emitting the whole catalog

@agentproto/apps also ships an agentproto-apps-sync binary that emits every bundled app to disk and writes a flat catalog:

npx agentproto-apps-sync [--base-dir <dir>]

The default base directory is ~/.agentproto/apps. It writes each app's manifests under <baseDir>/<slug>/ and a summary catalog to <baseDir>/../app-catalog.json (so ~/.agentproto/app-catalog.json by default).

Generic by design

Team ids are @agentproto/… and depend on no product package (the architecture invariant: nothing under @agentproto/* may import an app's @<app>/core). That's what lets any host — including agentik-studio — import a team and use its agents/workflows directly.