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

universal-agents

v0.3.0

Published

Universal Agents CLI utilities

Readme

Universal Agents

This repository hosts the canonical rules and skills every Universal Agent must follow so that behavior stays consistent across runtimes. By mirroring the contents of .agents/ and AGENTS.md, any agent can reboot into a known-good configuration and collaborate with peers safely.

CLI

Use npx universal-agents (no global install required).

CLI commands

| Command | Description | | ----------------------------------- | -------------------------------------------------------------------------------- | | npx universal-agents init | Copies the repository’s AGENTS.md template into the current working directory. | | npx universal-agents create skill | Prompts for a skill name and creates .agents/skills/<name>/SKILL.md. | | npx universal-agents create rule | Prompts for a rule name and creates .agents/rules/<name>.md. |

Why Universal Agents?

Different AI coding assistants use different conventions to organize their configuration files. For example:

  • Claude Code stores skills in .claude/skills/<skill-name>/SKILL.md
  • Cursor stores rules in the .cursor/rules/ folder

This fragmentation means agents cannot easily share or reuse configurations from one another.

Universal Agents solves this by providing a unified structure for organizing rules and skills that works across all AI coding assistants.

Reference layout

| Path | Purpose | | ---------------- | ----------------------------------------------------------------------------------------------------------------- | | AGENTS.md | Control manifest describing the execution protocol, how to load skills/rules, and the required response contract. | | .agents/skills | Like functions — they let the AI agent execute specific actions. | | .agents/rules | Like conventions — they inform the AI agent about the guidelines of the codebase. |

Execution protocol

  1. Always read AGENTS.md first to understand which skills or rules apply before starting a task.
  2. Load skills on demand: read skills/*/SKILL.md only when its trigger matches the task, then follow the prescribed workflow and output format.
  3. Enforce rules whenever relevant: if a task touches REST APIs, React components, or Git commits, preload the corresponding .agents/rules/*.md file and ensure all advice respects it.
  4. Declare context in responses: every reply must list which skills and rules were activated so users know which guardrails were applied.

Visual references

| Asset | Codex | Claude code | | ------- | ---------------------------------- | ------------------------------------------- | | Preview | Codex diagram | Claude code view |

Following this structure ensures every Universal Agent bootstraps with the same knowledge base, yielding predictable, rule-compliant collaboration.

Rules vs. skills in plain language

| Aspect | Rules (Cursor-style) | Skills (Claude-style) | | ---------------- | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | Content type | Textual guardrails (e.g., “use python-docx, add a title, keep formatting tidy”). | End-to-end package with docs, runnable templates, and tooling (often sourced from /mnt/skills/.../SKILL.md). | | Execution effort | Agent interprets and implements instructions manually. | Provides production-tested code snippets, patterns, and edge-case playbooks ready to drop into a task. | | Use case | Keeps behavior aligned with policies and coding standards. | Speeds up specialized workflows by handing the agent a toolbox plus demo-quality walkthroughs. | | Maintenance | Update the prose rule whenever governance changes. | Refresh the skill bundle when better implementations or examples land; the structure makes verification simpler. |

In short:

  • Rules are the “manual”
  • Skills are the “manual + toolbox + show-and-tell” kit you reach for when the task demands more than guidelines.

Apply Universal Agents in Claude Code

Claude Code sometimes ignores its CLAUDE.md file and doesn't support the AGENTS.md protocol. Use a user memory prompt to force loading:

ALWAYS read AGENTS.md file first

In Claude, pin this via the /memory command so it stays in user memory.