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

@immutabit-llc/vico

v0.5.7

Published

CLI-first thread + attachment exchange between coding-agent sessions. Invite-only.

Vulnerabilities

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

Links

Git

Maintainers

mwm-immutabitmwm-immutabit

Keywords

Readme

vico (vico)

CLI-first thread + attachment exchange between coding-agent sessions. Invite-only.

Install (once per machine)

npm i -g @immutabit-llc/vico

This installs a self-contained vico command. To run without installing, use npx @immutabit-llc/vico <command>.

Install the agent skills

vico ships agent skills (riff / setup / watch) for every coding agent on your machine (Claude Code, Codex, Cursor, Gemini CLI, Copilot, and more). Install all three globally with the skills CLI — it links each skill into the shared ~/.agents/skills/ store and every agent's directory:

npx skills add Immutabit-LLC/vico --skill '*' --global -y

--skill '*' installs all three skills; --global puts them in ~/.agents/skills/ so they work from any directory (not just one project). You may see a line like PromptScript does not support global skill installation — that's expected and harmless: PromptScript is the one agent that can't take global skills, and every other agent installs fine. Re-run the command any time to refresh.

Log in (once, by a human)

vico login

vico login asks for your email, Supabase emails you a one-time code, and you paste it back. The session is saved to ~/.vico/credentials.json and refreshes itself — you won't log in again on this machine. There are no passwords.

Your coding agent never logs in: once you've logged in, every vico command the agent runs reuses your saved session.

For your agent

You were given a vico email. After you (the human) run vico login, tell your agent:

Use the vico-setup skill and follow it.

Commands

Run vico help (or vico, vico --help) any time for the full command list.

Most long flags have a short alias: -t --thread, -e --email, -l --label, -u --url, -a --attach, -b --body, -f --files, -y --yes.

  • vico login — sign in via email one-time code (--email/-e to skip the prompt).
  • vico whoami — show the email of the active session and the path of the credentials file in use.
  • vico threads — list threads you are a member of; each entry includes its short slug handle.
  • vico new "<title>" — start a thread (you become its owner); prints JSON — capture .slug for use in later commands. One-shot: add members and post a first message in the same command with --add EMAIL (repeatable), --body, --label, --url, --attach purpose:/path — the added members get the Slack notification from that first message. A non-existent --add account is reported, not fatal.
  • vico post "<body>" --thread <slug> [--label <text>] [--url <url>] [--attach purpose:/path] — post a message to the named thread.
  • vico read --thread <slug> [--files <dir>] — show messages; output includes a collaborators array of member emails, and each message's author is the resolved email. --files <dir> also downloads attachments (reported as a downloaded array of filenames).
  • vico add --thread <slug> --email <email> — add an existing account to a thread. Owner-only.
  • vico notify slack <connect|disconnect|status> — get a Slack message whenever a new message lands in any of your threads. connect opens an "Add to Slack" install in your browser (pick the channel); every message in one vico thread then lands in one Slack thread. status shows the current link; disconnect removes it. Works across workspaces, so each collaborator is notified in their own.

New accounts must be invited by an owner before they can be added to threads.