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

agent-trellis

v0.9.1

Published

A unified Code Agent Runtime for Skills, MCP, Memory, and shared instructions across Claude Code, Codex, Kiro, pi, Kimi Code, and ZCode.

Readme

Trellis

One canonical source for Skills, MCP, Memory, and shared instructions — projected safely into Claude Code, Codex, Kiro, pi, Kimi Code, and ZCode.

中文:一个 canonical source 统一管理多个 Code Agent 的 Skill、MCP、Memory 与共享指令,支持预览、备份与回滚。

Agent Trellis — One Runtime. Every Code Agent.

Quick start

npm install -g agent-trellis

trellis onboard --dry-run   # preview: migration source, managed agents, MCP, memory
trellis onboard             # apply — every write is backed up automatically
trellis doctor              # verify state, any time

# import a GitHub Skill into Trellis canonical storage, then sync it
npx trellis add mattpocock/skills --skill loop-me --dry-run

Something went wrong? trellis rollback inverts the last run.

How it compares

| | Skills / Rules | MCP | Memory | Secret hygiene | Agents covered | |---|---|---|---|---|---| | ai-rules, skills-link, agent_sync | ✅ | ❌ | ❌ | ❌ | Many — but not Kiro or pi | | skillshare, skills-hub | ✅ skills only | ❌ | ❌ | ❌ | Codex, Claude, … | | mcp-router | ❌ | ✅ desktop router | ❌ | config in its own dashboard | — | | MetaMCP, mcp-hub | ❌ | ✅ aggregator | ❌ | ❌ | — | | cli-agent-orchestrator | ❌ | ❌ | ❌ | ❌ | Runs agent fleets, doesn't unify config | | Trellis | ✅ | ✅ native config, Runtime, or hub mode | ✅ shared memory + handoffs | ✅ references only, secrets audit | Claude Code, Codex, Kiro, pi, Kimi Code, ZCode |

Sync tools stop at rules and skills. MCP routers manage servers but hold their own config — a second source of truth (we hit real token drift with exactly that setup). Trellis is the only one treating Skills + MCP + Memory + instructions as one canonical system, and the only one covering Kiro and pi. Full landscape survey: docs/research.md.

Design principles

  1. One canonical source, many adapters — agent-native configs are generated artifacts, never hand-edited.
  2. No plaintext secrets, ever — outputs hold variable references; trellis secrets audit rejects raw values.
  3. Verify, don't assume — every adapter claim is backed by an executed probe in isolated Docker sandboxes, never a developer's own dotfiles.

Trellis aligns with the emerging .agents Protocol draft rather than inventing another standard.

Docs

Status

Early, pre-1.0. All CLI commands are implemented, unit-tested, and verified against real agents in isolated containers. Known limitations are listed in Getting started; please open an issue for anything a clean-room sandbox wouldn't catch.

License

MIT — see LICENSE.