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

relic-cli

v2.2.1

Published

Shared project knowledge for coding agents

Readme

relic-cli

Shared project knowledge for coding agents — npm distribution.

Relic keeps the current boundary of a project's knowledge in the repository. One central skill helps coding agents challenge ideas, explore the code, and persist only the requirements, decisions, epics, shared knowledge, and specifications the developer chooses to keep.

Install

npm install -g relic-cli

Requires Node.js 18+. One-off usage also works:

npx relic-cli init

Getting started

cd my-project
relic init
relic install --engine codex

Supported engines are claude, copilot, codex, and agents. The codex target installs in .codex/skills; the portable agents target installs in .agents/skills. Every target receives the same reasoning contract, while host-specific metadata stays with its host. Installation does not create or edit AGENTS.md, application documentation, or agent-owned configuration.

Then ask the agent naturally:

Use Relic to roast this feature before we implement it.

Ambient skill discovery may invoke Relic without naming it. The explicit form above is the portable fallback across supported agents.

CLI

| Command | Purpose | |---|---| | relic init [--dir path] | Create the root relic.yaml topology | | relic install [--engine claude\|copilot\|codex\|agents] | Install or refresh the central skill | | relic search <query...> [--json] | Search the complete current Relic corpus | | relic serve [--port number] | Open the read-only interactive knowledge viewer |

Without --engine, install refreshes the supported project-local engine roots that already exist.

Also available via uv / pip

uv tool install relic-cli
pip install relic-cli

Full documentation · Report an issue