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

opencode-ask

v1.1.0

Published

Ask Agent for OpenCode — Q&A about your codebase, inspired by GitHub Copilot's /ask

Downloads

138

Readme

Ask — Code Q&A for OpenCode

Ask is a read-only Q&A agent for OpenCode. It answers questions about your codebase — explains how things work, finds relevant code, explores architecture, and provides deep insights — without ever editing your files.

Powered by your existing OpenCode model. No extra API keys. No subscriptions.


Quick Start

Install

  1. Clone this repo or download ask.js
  2. Copy or symlink ask.js to your OpenCode config plugins:
    mkdir -p ~/.config/opencode/plugins
    cp ask.js ~/.config/opencode/plugins/ask.js
  3. Add to ~/.config/opencode/opencode.json:
    {
      "plugin": ["./plugins/ask.js"]
    }
  4. Restart OpenCode.

Use

Ask is available both as a general agent (selectable in OpenCode's agent picker) and via @ask in any conversation:

  • General mode — Select "Ask" from the agent list for a dedicated Q&A session
  • Subagent mode — Type @ask how does collision work? mid-conversation

Ask will explore the codebase, gather context, and give you a thorough answer — complete with file paths, line numbers, and architectural context.


How It Works

Ask is an OpenCode plugin that registers a subagent named ask. When invoked, the agent:

  1. Explores — searches your codebase with grep, glob, and targeted file reads
  2. Analyzes — traces code paths, understands architecture, identifies patterns
  3. Answers — provides a clear, structured response with source citations
  4. Never edits — the agent has edit: deny and write: deny baked in

vs. GitHub Copilot /ask

| | GitHub Copilot /ask | OpenCode Ask | |---|---|---| | Scope | Current file + editor selection | Full workspace exploration | | Search tools | None (inline context only) | grep, glob, read, bash, web | | Architecture awareness | Limited to visible code | Deep — traces across files and layers | | Permission model | Read-only by convention | Enforced: edit: deny, write: deny | | Invocation | In-editor chat panel | @ask in any OpenCode conversation | | Model | Copilot's model | Your configured OpenCode model | | Subagent dispatch | No | Yes — can delegate parallel searches via task | | Custom prompt | Fixed | Open source — fork and customize | | Offline | No (cloud only) | Depends on your model provider |

When to use which

Use Copilot /ask when you need a quick answer about the file or selection you're actively editing — minimal context switching.

Use OpenCode Ask when you need deep understanding — tracing logic across many files, understanding architecture, investigating bugs, or orienting yourself in an unfamiliar codebase.


Permissions

| Tool | Access | |------|--------| | read | allow | | grep | allow | | glob | allow | | bash | git *: allow, *: ask | | webfetch | allow | | websearch | allow | | task | allow | | edit | deny | | write | deny |


License

MIT