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

@ar-ai/brink-cli

v1.0.7

Published

Local AgentRouter proxy and guided setup for Claude Code and Codex.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

creepingpacketcreepingpacket

Keywords

Readme

Brink

Made by rexy and brink. Brink is a local AgentRouter proxy for Claude Code and Codex. It provides guided client setup, protocol bridges, bounded retries for transient provider failures, and a terminal dashboard.

Install and run

Install Node.js 24 or newer with npm, then install Brink:

npm install --global @ar-ai/brink-cli
brink

On first run, Brink opens guided setup and starts the proxy after setup succeeds. Choose Claude Code, Codex, or both; enter your own AgentRouter API key at the hidden prompt and select a model. Setup can install a missing selected client. npm installation itself only installs Brink; it does not ask for credentials or change client settings.

Keep Brink open. In a second terminal, open your project and run claude or codex. Use /model inside the client. The proxy listens on 127.0.0.1:8787 by default. Stop it with Ctrl+C.

You can also run Brink without a global installation:

npx @ar-ai/brink-cli

For a project-local installation, use npm install @ar-ai/brink-cli, then npx brink. The runtime supports Windows, macOS, and Linux; selected client installers require a supported 64-bit platform.

Commands

| Command | Purpose | | --- | --- | | brink | Start the proxy, opening setup on first run. | | brink setup | Install/connect clients or change models. | | brink start --plain | Start the proxy with ordinary line logs. | | brink check | Repair Brink-managed client settings. | | brink update | Replace the saved API key through hidden input. | | brink art | Display the supplied artwork. | | brink --help | Display help. |

brink update changes credentials. To update the software, stop Brink and run npm install --global @ar-ai/brink-cli@latest.

Settings are saved in ~/.config/brink/config.json (or BRINK_CONFIG_HOME). Setup also writes selected clients' user settings. Credentials are stored locally without encryption; Windows file access follows your profile permissions. Model access, quota, and billing remain controlled by AgentRouter.