prpm-json-best-practices

A set of rules for writing prpm.json files, which describe packages published through PRPM, a package manager for prompts, rules, skills, and agents.

In plain words
What is it for?
Use it when publishing packages, creating package collections, distributing your own add-ons, or managing multiple packages in one repository.
Why use it?
It helps package authors include the required information and organize related packages correctly, including packages stored in a monorepo, a repository containing several related packages.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/pr-pm/prpm/prpm-json-best-practices
Clone the repo
git clone --depth 1 https://github.com/pr-pm/prpm

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,654 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03654
Opus 5 $0.00000 $0.01827
Sonnet 5 $0.00000 $0.00731
Haiku 4.5 $0.00000 $0.00365

Measured 3d ago against content hash 308367feffbd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

prpm-json-best-practices scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/prpm-json-best-practices.mdc · 541 lines

How it starts

The opening of the file, as written. The whole thing — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.

PRPM JSON Best Practices

Best practices for creating and maintaining prpm.json package manifests for PRPM (Prompt Package Manager).

Core Purpose

prpm.json is only needed if you're publishing packages. Regular users installing packages from the registry don't need this file.

Use prpm.json when you're:

  • Publishing a package to the PRPM registry
  • Creating a collection of packages
  • Distributing your own prompts/rules/skills/agents
  • Managing multiple related packages in a monorepo

File Structure

Single Package

{
  "name": "my-awesome-skill",
  "version": "1.0.0",
  "description": "Clear, concise description of what this package does",
  "author": "Your Name <[email protected]>",
  "license": "MIT",
  "repository": "https://github.com/username/repo",
  "organization": "your-org",
  "format": "claude",
  "subtype": "skill",
  "tags": ["typescript", "best-practices", "code-quality"],
  "files": [
    "SKILL.md"
  ]
}

Note: When "organization": "your-org" is specified, the registry automatically prefixes the package name with @your-org/, so this package will be published as @your-org/my-awesome-skill and installed with prpm install @your-org/my-awesome-skill.

Multi-Package Repository

{
  "name": "prpm-packages",
  "version": "1.0.0",
  "author": "Your Name",
  "license": "MIT",
  "repository": "https://github.com/username/repo",
  "organization": "your-org",
  "packages": [
    {
      "name": "package-one",
      "version": "1.0.0",
      "description": "Description of package one",
      "private": true,
      "format": "claude",
      "subtype": "agent",
      "tags": ["tag1", "tag2"],
      "files": [".claude/agents/package-one.md"]
    }
  ]
}

Required Fields

Single Package

Field Type Required Description
name string Yes Package name (kebab-case, unique in registry)
version string Yes Semver version (e.g., 1.0.0)
description string Yes Clear description of what the package does
author string Yes Author name and optional email
license string Yes SPDX license identifier (e.g., MIT)
format string Yes Target format: claude, cursor, continue, windsurf
subtype string Yes Package type: agent, skill, rule, slash-command, prompt
files string[] Yes Array of files to include in package

Read the full file on GitHub · 541 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 541 lines · 0 tokens per session scan A 308367feffbd

Subscribe to this mod's changes

prpm-json-best-practices is a cursor rule published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,654 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.