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

agent-secret-manager

v0.1.1

Published

Agent-native local secret request CLI and bundled Codex skill.

Readme

agent-secret-manager

Agent-native secret requests for local projects.

agent-secret-manager gives coding agents a structured way to ask a human for API keys without pasting values into chat or terminal output. The CLI starts a localhost form, the human enters the value, and the CLI writes it into a local .env file with private file permissions.

Quick start

npx agent-secret-manager request OPENAI_API_KEY --reason "Run the local OpenAI example"

The command prints and opens a localhost URL. The --reason text is shown in the form so the human can see why the agent is asking. After the form is submitted:

  • .env contains the secret value.
  • .env.example contains blank keys for agent-readable setup.
  • .gitignore ignores .env, .env.*, and .agent-secret-manager/.
  • .agent-secret-manager/manifest.json records metadata only, never values.

Verify without printing values:

npx agent-secret-manager check OPENAI_API_KEY

Run a command with the env file loaded:

npx agent-secret-manager run -- npm test

Structured requests

Agents can create a request spec with no secret values:

{
  "title": "Project secrets",
  "reason": "The test suite calls external APIs.",
  "envFile": ".env",
  "exampleFile": ".env.example",
  "secrets": [
    {
      "name": "OPENAI_API_KEY",
      "label": "OpenAI API key",
      "reason": "The integration tests call OpenAI.",
      "help": "Create a project key in the OpenAI dashboard.",
      "required": true
    }
  ]
}

Then run:

npx agent-secret-manager request --from secrets.request.json

Commands

agent-secret-manager init [--env .env]
agent-secret-manager request <ENV_NAME...> [--reason text] [--env .env]
agent-secret-manager request --from secrets.request.json
agent-secret-manager check <ENV_NAME...> [--env .env]
agent-secret-manager list [--env .env]
agent-secret-manager run [--env .env] -- <command>
agent-secret-manager spec <ENV_NAME...>
agent-secret-manager skill path
agent-secret-manager skill install

Skill distribution

The package includes a Codex skill in skills/agent-secret-manager.

Install it from an npm install:

npx agent-secret-manager skill install

The skill tells agents to request missing secrets through this CLI, verify only presence, and avoid opening or printing the .env contents.

Security model

This tool prevents routine secret exposure in prompts, screenshots, shell history, and agent logs. It stores secrets as plaintext in a local env file because that is what most local development tools already consume. It is not a sandbox boundary against a malicious local process or an agent that is explicitly instructed to read secret files.