PRPM CLI
A package manager for AI agents that installs rules, skills and prompts and converts them for Cursor, Claude Code and others.
- 124 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI writes third-party rules and skills into project folders and changes agent behaviour, and search queries go to the registry server.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/prpmDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI writes third-party rules and skills into project folders and changes agent behaviour, and search queries go to the registry server.
This is third-party code. Review the repository files before installing.
What it does
PRPM installs rules, skills, agents, slash commands and prompts from a shared registry. On install a package is converted into the target tool's format: rules land in `.cursor/rules/`, skills in `.claude/skills/`, instructions in `.github/instructions/` and so on. The format is chosen with `--as`; without it PRPM detects the editor from project files. Search works by keyword (`prpm search`) or in natural language (`prpm ai-search`, free and without sign-in). Collections install as whole sets, for example `prpm install collections/nextjs-pro`. An author describes a package in a `prpm.json` file and publishes it with `prpm publish`. For agents the README has a short cheat sheet: search needs the `--no-interactive` flag.
Who it is for. Teams where some developers use Cursor and others Claude Code or Copilot, and agent rules need to stay the same for everyone.
Good fit when
- You need a set of Next.js rules from a collection in one command.
- The same skill is installed into Cursor, Claude Code and Windsurf in their own formats.
- An agent is tasked with finding a useful package itself through `prpm ai-search`.
- Your own rule set from `.cursor/rules/` is published so a team can install it in one command.
Not a fit when
- Rules and skills must be reviewed line by line: third-party packages shape agent behaviour.
- One format in one tool is enough and manual copying is simpler.
- The network is closed: the registry runs on the project's servers.
Example request
Find a React with TypeScript rule package through prpm, show its description with info and install it in Claude Code format.Limitations
Node.js and npm are needed for `npm install -g prpm`. Registry packages are written by third parties and change agent behaviour: inspect them with `prpm info` before installing. Conversion happens server-side, so a network is required. The Playground for trial runs needs sign-in, and the README names free monthly credits. Agents need the `--no-interactive` flag for `prpm search`, otherwise output stops at interactive prompts. The last commit dates from October 2026.
How to disable. Delete installed packages from their install locations (for example `.cursor/rules/`, `.claude/skills/`) and remove the CLI with `npm uninstall -g prpm`.
FAQ
How do I install PRPM?
Run `npm install -g prpm`. Then `prpm install collections/nextjs-pro` installs a collection of 20 packages and `prpm install <package>` a single one.
Where does PRPM put files for Claude Code and Cursor?
For Claude Code skills go to `.claude/skills/`, commands to `.claude/commands/` and agents to `.claude/agents/`. For Cursor rules go to `.cursor/rules/`.
How do I install a package in another format?
Add the `--as` flag, for example `prpm install @sanjeed5/react --as cursor`. `--subtype` sets the subtype: `rule`, `agent`, `skill`, `slash-command`, `hook` and others.
How do I publish my own rules?
Run `prpm init`, check with `prpm publish --dry-run` and publish with `prpm publish`. The `prpm.json` manifest holds the name, format, subtype and files.
Is sign-in needed for search?
No. `prpm ai-search` with a natural-language query is free and works without sign-in. Sign-in is needed for the Playground.
Discussion
No questions or reviews yet.
Related
CLI toolsAPM
APM (Agent Package Manager)
A package manager for AI agent context: skills, prompts and MCP servers install with one command across supported agents
Eleven skills take an agent from an idea to verified code through a PRD and RFCs kept as files in the repository
A CLI that keeps agent instructions in one place and distributes them to the right config files for Claude Code, Cursor, Codex, Copilot and two dozen other tool
rpa-gen-rules: project rules for agents
rpa-gen-rules
Skill that generates matching project rules for Cursor, Claude Code and Codex built around layered development and BDD
Python runtime for agent work: task boundaries, independent verification of results and a saved handoff between sessions
agr is a package manager for agent skills: installs them from any Git repo into Claude Code, Cursor and Codex by a versioned manifest, like npm or uv
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| PRPM (this card) | no | 124 | |
| Rulesync | no | 1,586 | spreads one local rule source across tool configs; PRPM installs third-party packages from a registry and converts them |
| SkillKit | no | 1,574 | a skill manager that installs from repositories; PRPM adds a registry with search, collections and publishing of rules and prompts |
README in short
The README runs from installation and an agent cheat sheet to the format table, search, collections, the playground and publishing. It lists install locations for each editor.