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

@glaicer/supercode-skill-commands

v0.3.0

Published

OpenCode plugin that registers your agent skills as commands so they show up in / autocomplete

Readme

skill-commands

An OpenCode plugin that makes your skills show up in / autocomplete.

The problem

Typing /my-skill works. Typing / doesn't list it.

OpenCode does register your skills as commands, but the TUI hides them from the autocomplete popup, so a skill is only reachable if you already remember its name — or you go through the /skills picker (palette entry prompt.skills, bindable as "keybinds": { "prompt_skills": "..." } in tui.json).

This plugin re-registers each skill as an ordinary command, so it shows up in the popup like everything else. Same name, same behaviour, no duplicates — a real command simply wins over the skill entry of the same name.

Restart OpenCode after saving.

Which skills it picks up

Parity with OpenCode's runtime (~/.opencode/bin/opencode SkillDiscovery):

  • ~/.agents/skills/**/SKILL.md and ~/.claude/skills/**/SKILL.md (global, dot:true, symlink:true)
  • <session-dir>/.agents/skills/**/SKILL.md and <session-dir>/.claude/skills/**/SKILL.md walked up to the worktree root (** recursive, dot + symlink, cycle-safe via realpath)
  • opencode.jsonc: skills.paths (each entry scanned **/SKILL.md; ~/ expanded, relative resolved against worktree)

Project bases come first (nearest dir → worktree → global), .agents before .claude at each level, so a nearer or .agents skill shadows a farther / .claude one. A duplicate name is registered once (config.command[name] first-wins, same dedup as OpenCode's duplicate skill name warning). The walk stops at the worktree root, so nothing above your repo leaks in.

Not mirrored (require live fetch / plugin host): skills.urls and plugin-provided {skill,skills}/**/SKILL.md directories.

Install

Install with the OpenCode CLI:

opencode plugin @glaicer/supercode-skill-commands --global
  • --global installs into the global config (~/.config/opencode); default is local (.opencode in the current project).
  • --force replaces an already-installed version.
  • Restart OpenCode after installing.

Manual install also works: add the package to the plugin array in opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@glaicer/supercode-skill-commands"]
}