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

@hantengry/opencode-agile-team

v0.0.8

Published

OpenCode plugin for Agile Team MCP utilities.

Readme

OpenCode Agile Team

Streamlit app for visualizing OpenCode model/agent configs plus a portable OpenCode plugin package for Agile Team MCP utilities.

Streamlit App

Run the visualizer locally:

make run

The Mock Time sidebar writes an ISO-8601 value to ~/.config/opencode/agile_team/mock_time.json. The MCP time tool reads the same file and falls back to real current time when no mock value is configured.

OpenCode Plugin

This repo is prepared as npm package @hantengry/opencode-agile-team.

The plugin entrypoint is opencode/plugin/agile-team-plugin.ts. Its OpenCode config hook registers one local MCP server named agile-team using:

{
  "type": "local",
  "command": ["uv", "run", "--with", "mcp", "python", "<package>/mcp/server/app.py"],
  "enabled": true
}

The MCP server entrypoint is mcp/server/app.py. Tool handlers live under mcp/handlers/:

  • current_time: reports the current time or configured mock time.
  • admin_url: returns the Streamlit admin URL from ~/.config/opencode/agile_team/admin.json.

The server uses the official Python MCP SDK (mcp). The npm plugin launches it through uv run --with mcp ... so the Python SDK can be resolved at runtime. Systems testing the npm plugin need uv available on PATH.

When the MCP server starts, it also starts the Streamlit admin app in the background. It chooses the first available localhost port from 8501 upward and writes one status line to stderr, for example Agile Team admin started at http://localhost:8501. Child Streamlit logs and launcher state live under ~/.config/opencode/agile_team/admin.log and ~/.config/opencode/agile_team/admin.json. MCP stdout remains protocol-only.

Local OpenCode Registration

For local testing, register the plugin file into global OpenCode config:

make init

This safely adds the local plugin path to ~/.config/opencode/opencode.json if absent and avoids duplicate plugin entries. Restart OpenCode after running it because OpenCode config is loaded only on startup.

After npm publication, global OpenCode config can use only the package name:

{
  "plugin": ["@hantengry/opencode-agile-team"]
}

The package plugin registers the MCP server under the hood, so direct global mcp registration is no longer the intended architecture.

Publishing

Inspect package contents without publishing:

make pack-dry-run

Publish a patch release while the version remains 0.0.x:

make push

Publish larger bumps explicitly:

make push-minor
make push-major

make push intentionally fails once the package version is no longer 0.0.x; use the explicit minor or major target then. None of these commands should be run unless you intend to publish to npm.