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

aci-codex-connect

v0.1.0

Published

Installer for AI Context Intelligence Codex Connect.

Vulnerabilities

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

Links

Maintainers

fnnikitafnnikita

Keywords

Readme

ACI Connect CLI

Installer for AI Context Intelligence Codex Connect.

Target command after publishing:

npx aci-codex-connect setup

Local development command from this repository:

node tools/aci-connect/bin/aci-connect.js setup --app-url http://127.0.0.1:8765/app

The installer:

  1. creates a short-lived ACI setup session;
  2. opens ACI in the browser;
  3. waits for the signed-in user to approve pairing;
  4. receives a one-time tenant MCP token;
  5. stores the token outside config.toml using ACI_MCP_TOKEN;
  6. writes the ACI MCP server block to ~/.codex/config.toml;
  7. installs an ACI rule in ~/.codex/AGENTS.md;
  8. installs an ACI skill in ~/.agents/skills/aci-connect/SKILL.md.

The CLI does not receive the user's web auth session. It only receives the tenant MCP token created for Codex.

On macOS, the default secure path stores the token in Keychain, sets ACI_MCP_TOKEN for future GUI apps through launchctl, and installs a shell loader for new Terminal sessions. Fully quit and reopen Codex or the IDE after setup so the MCP server can read ACI_MCP_TOKEN.

The generated Codex MCP config uses:

[mcp_servers.aci]
url = "https://your-aci-host.example/mcp"
bearer_token_env_var = "ACI_MCP_TOKEN"
enabled = true
default_tools_approval_mode = "prompt"

It must not store the raw bearer token in ~/.codex/config.toml.