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

@w33ble/opencode-facts

v1.0.0

Published

Readme

opencode-facts

Inject markdown file contents into your OpenCode system prompt — above or below the default prompt.

Install

Add to opencode.json:

{
  "plugin": ["opencode-facts"]
}

For local development:

bun run build
mkdir -p .opencode/plugins
ln -sf $(pwd)/dist/index.js .opencode/plugins/opencode-facts.ts

Configuration

Project (takes precedence): .opencode/opencode-facts.json

Global (fallback): ~/.config/opencode/opencode-facts.json

{
  "top": ["CONTEXT.md", "docs/conventions.md"],
  "bottom": ["docs/glossary.md"]
}

| Field | Type | Description | |-------|------|-------------| | top | string[] | File paths injected right after the provider header (early, high-salience) | | bottom | string[] | File paths appended at the end of the system prompt |

Paths are relative to the project root. Absolute paths also work.

How it works

  1. At startup, the plugin reads your config and loads all listed files into memory.
  2. On every LLM call, file contents are injected into the system prompt — top files spliced in early, bottom files appended at the end.
  3. No XML wrapping, no frontmatter parsing — your markdown is injected as-is.

Build & Publish

bun run build          # tsup -> dist/index.js + dist/index.d.ts

tsup traces imports from src/index.ts — only reachable code lands in the bundle. @opencode-ai/plugin is marked external, so consumers resolve it from their own install.

Only dist/ ships (controlled by "files").

bun publish --access public

Requirements