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

@abhinav26104/agent-index

v0.2.0

Published

Deterministic repository context for AI coding agents

Readme

@abhinav26104/agent-index

A deterministic, security-conscious repository index for any AI coding agent. It uses local repository metadata, without an LLM, API key, or external service.

One-file workflow

Run these commands from the repository you want to index:

npx @abhinav26104/agent-index init .
npx @abhinav26104/agent-index sync .
npx @abhinav26104/agent-index check .

init creates .indexAgent/index.md. sync refreshes its managed section, while preserving user content outside the managed markers. check exits 0 when the index is current and 1 when it is stale. Use --dry-run to preview changes or --json for machine-readable output.

Tell your coding agent to read .indexAgent/index.md before working. The index describes the project, technologies, frameworks, package managers, commands, entry points, important directories, structure, tests, and configuration files. Source code, tests, and configuration remain the final source of truth.

Generated file

.indexAgent/
  index.md

The generated section is enclosed by <!-- agent-index:start --> and <!-- agent-index:end -->. User content before, after, or around that section is preserved.

Upgrading from 0.1.x does not remove or modify .agent-index, AGENTS.md, CLAUDE.md, GEMINI.md, context files, or legacy configuration. Remove those legacy files manually if they are no longer needed.

Safety and determinism

The scanner respects .gitignore, uses a safe manifest and README allowlist, and does not read arbitrary source-code contents. It excludes secrets, credentials, environment files, private keys, certificates, dependencies, builds, and generated files; does not follow symbolic links; rejects symlinked output paths; enforces depth and file-count limits; and normalizes paths across operating systems.

Output is sorted, timestamp-free, atomic, and idempotent. No production dependency is added for indexing.

Local development

npm install
npm run typecheck
npm test
npm run build

Licensed under the MIT License.