Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/pr-pm/prpm/prpm-json-best-practices)<a href="https://agentmods.dev/skills/pr-pm/prpm/prpm-json-best-practices"><img src="https://agentmods.dev/badge/skills/pr-pm/prpm/prpm-json-best-practices.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.08530 |
| Opus 5 | $0.00021 | $0.04265 |
| Sonnet 5 | $0.00008 | $0.01706 |
| Haiku 4.5 | $0.00004 | $0.00853 |
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 7d 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.
This is a copy
100% identical to prpm-json-best-practices — 296 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRPM JSON Best Practices
You are an expert at creating and maintaining prpm.json package manifests for PRPM (Prompt Package Manager). You understand the structure, required fields, organization patterns, and best practices for multi-package repositories.
When to Apply This Skill
Use when:
- Creating a new
prpm.jsonmanifest for publishing packages - Maintaining existing
prpm.jsonfiles - Organizing multi-package repositories
- Adding or updating package metadata
- Ensuring package manifest quality and completeness
Don't use for:
- User configuration files (
.prpmrc) - those are for users - Lockfiles (
prpm.lock) - those are auto-generated by PRPM - Regular package installation (users don't need
prpm.json) - Dependencies already tracked in lockfiles
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
See examples/single-package.json for complete structure.
Key fields: name, version, description, author, license, format, subtype, files
Multi-Package Repository
See examples/multi-package.json for complete structure.
Use when: Publishing multiple related packages from one repo
Key difference: Top-level packages array with individual package definitions
Collections Repository
See examples/collections-repository.json for complete structure.
Use when: Bundling existing published packages into curated collections Key points:
collectionsarray references packages bypackageId(not files)- Each collection has
id,name,description,packages - Packages can be
required: true(default) orfalse(optional) - Use version ranges (
^1.0.0) orlatest - Add
reasonto explain why package is included
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 1,218 lines · 42 tokens per session scan A 830ecbdb30c7
prpm-json-best-practices is a skill published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 8,530 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to prpm-json-best-practices, differing in 296 lines, and is treated as a copy.
Other skills, from other repositories
dependency-analysis
This rule automatically analyzes dependencies before they're installed to provide insights about maintenance frequency, security vulnerabilities, and popularity in the developer ecosystem.
biome
Biome JavaScript/TypeScript linter and formatter.
nextjs-react19
Next.js with React 19 App Router patterns.
laravel
Laravel PHP framework best practices.
android-new-project
Workflow for turning a fresh copy of this Android template into a new app — renaming the package/namespace/applicationId, branding (icons, splash, palette, fonts), Firebase setup, signing config, stripping unused sample screens, and verifying the foundation. Use when the user says they are starting a new app…
template-helpers
Catalog of the reusable building blocks shipped with this Android template — BaseActivity/BaseFragment, the helpers/ extension files (navigation, lifecycle, toast, snackbar, dialogs, images, permissions, theme, locale, settings intents, date, delay), common/ (Firebase, network, observers), and…