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

@cdbattags/ai

v1.0.5

Published

User-level AI agent configuration: rules, skills, MCP profiles, and multi-tool deployment

Readme

ai

User-level AI agent configuration: Cursor rules and skills, Claude Code config, OpenCode config, and composable MCP server profiles. One repo, symlinked everywhere.

Setup

Requires Node.js 22.6+ (native TypeScript execution).

git clone --recurse-submodules [email protected]:cdbattags/ai.git ~/ai
cd ~/ai && npm install

node link.ts              # build dist/ + install to ~/
node link.ts --dry-run    # preview without changes

How it works

src/ holds authored content (rules, skills, tool configs, MCP server definitions).

vendor/ holds community repos as git submodules. Cherry-picks are declared in vendor.json.

dist/<name>/ is the assembled per-tool tree, built by link.ts. Each user gets their own directory (default: cdbattags). It contains relative symlinks back to src/ and vendor/; browsing dist/cdbattags/ on GitHub shows the full resolved config. Forkers can build their own with --name.

link.ts has two phases:

  1. build: Wipe dist/<name>/, recreate symlinks from src/ + vendor cherry-picks, generate mcp.json from profile
  2. install: Symlink dist/<name>/ contents into ~/.cursor/, ~/.claude/, ~/.config/opencode/ (or into cwd with --workspace)

Repository layout

src/
  rules/                        Cursor rules (.mdc)
  skills/                       Cross-tool skills (SKILL.md)
  cursor/commands/              Cursor-specific commands
  claude/                       Claude Code config (CLAUDE.md, settings, commands)
  opencode/                     OpenCode config (opencode.json)
  mcp/servers/                  Individual MCP server configs
  mcp/profiles/                 Named sets of servers

vendor/                         Git submodules (community rules/skills)
vendor.json                     Declares which vendor items to cherry-pick

dist/cdbattags/                 Built output (git-tracked symlinks per tool)
  cursor/                       -> ~/.cursor/
  claude/                       -> ~/.claude/
  opencode/                     -> ~/.config/opencode/

link.ts                         Build + install script

Rules

| Rule | What it does | |------|-------------| | direnv-shell-bootstrap | Bootstrap Nix/direnv in non-interactive Cursor shells | | git-commit-confirmation | Require explicit user approval before every commit | | gh-cli | Use gh CLI instead of raw API calls for GitHub operations | | github-repo-triage | Conventions for triaging issues/PRs, cherry-picks, releases | | documentation | README placement and docs/ folder structure | | markdownlint-compliance | Keep markdown files lint-clean | | no-sleep-process-monitoring | Use Shell tool waiting instead of sleep/polling | | install-latest-packages | Always resolve real latest versions when adding dependencies | | deduplicate-rules | Prevent overlap between user-level and project-level rules | | sandbox-domains | Network allowlist for Cursor sandbox | | use-trash-not-rm | Prefer recoverable trash over rm |

Skills

| Skill | Source | What it does | |-------|--------|-------------| | direnv-shell-commands | own | Cached direnv/Nix environment for fast shell bootstrap | | find-3d-assets | own | Find and integrate low-poly 3D models (GLB/GLTF) | | gh-cli | own | GitHub CLI patterns for PRs, issues, releases, API calls | | github-repo-triage | own | Full triage, cherry-pick, release, and publishing workflow | | markdownlint-compliance | own | Auto-fix and manual-fix guidance for markdownlint | | process-monitoring | own | Wait for processes without sleep or polling loops | | submodule-worktree | own | Manage git worktrees across repos and submodules | | karpathy-guidelines | vendor | Behavioral guardrails: think first, simplicity, surgical changes | | logging-best-practices | vendor | Structured logging and wide events (Stripe canonical log lines) | | test-driven-development | vendor | Red-green-refactor TDD with rationalization rebuttals |

MCP profiles

Compose per-workspace MCP configs from individual server definitions.

node link.ts build --mcp web        # build with 'web' profile
node link.ts build --mcp backend    # build with 'backend' profile

| Profile | Servers | |---------|---------| | base | context7, memory, sequential-thinking, fetch | | web | base + playwright | | backend | base + docker, sentry | | full | all servers |

Available servers: context7, docker, fetch, github, memory, playwright, sequential-thinking, sentry

Vendor submodules

Community rules and skills pulled in as git submodules under vendor/. Cherry-picks are declared in vendor.json.

| Vendor | Repo | Cherry-picked | |--------|------|---------------| | hutchic | hutchic/.cursor | karpathy-guidelines, logging-best-practices, test-driven-development | | aussiegingersnap | cursor-skills | (available; none selected yet) |

To cherry-pick a new vendor skill, add it to vendor.json and rebuild:

# Edit vendor.json, then:
node link.ts build

link.ts

Usage: node link.ts [command] [options]
       npx @cdbattags/ai [command] [options]

Commands:
  build               Build dist/<name>/ from src/ + vendor
  install [tool...]   Symlink dist/<name>/ into ~/ (cursor, claude, opencode, or all)
  (no command)        Build + install all

Options:
  --name NAME         Output directory under dist/ (default: cdbattags)
  --mcp PROFILE       MCP profile to use (default: base)
  --workspace         Install into cwd (.cursor/, .claude/) instead of ~/
  --dry-run           Show what would happen without doing it
  --clean             Remove installed symlinks
  -h, --help          Show this help

Forkers can build their own dist (gitignored) without touching the tracked one:

node link.ts build --name myname
node link.ts install --name myname

Workspace install (npx)

Install rules and skills into the current project instead of your home directory:

npx @cdbattags/ai install --workspace               # all tools
npx @cdbattags/ai install cursor --workspace         # cursor only
npx @cdbattags/ai install --workspace --dry-run      # preview
npx @cdbattags/ai install --workspace --clean        # remove

This creates .cursor/, .claude/, .opencode/ in cwd with symlinks back to the built dist. Useful for per-project overrides or sharing config across a team repo.

License

MIT