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.
npx agentmods add skills/pr-pm/prpm/documentation-standardsnpx skills add pr-pm/prpm --skill documentation-standardsgit clone --depth 1 https://github.com/pr-pm/prpmWhat 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 | $0.00036 | $0.01733 |
| Opus 5 | $0.00018 | $0.00866 |
| Sonnet 5 | $0.00007 | $0.00347 |
| Haiku 4.5 | $0.00004 | $0.00173 |
Grade A, and why
documentation-standards 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.
How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PRPM Documentation Standards
Documentation Organization
Internal Documentation (development/docs/)
Purpose: Documentation for developers working on PRPM itself
Location: development/docs/
Files:
GITHUB_WORKFLOWS.md- GitHub Actions workflows referencePUBLISHING.md- NPM package publishing process and orderDEVELOPMENT.md- Development setup, environment, and workflowsDOCKER.md- Docker setup, services, and troubleshooting
Audience: PRPM contributors, maintainers, CI/CD systems
User-Facing Documentation (docs/)
Purpose: Documentation for PRPM users and package authors
Location: docs/ (at project root)
Files:
- User guides
- API documentation
- Package authoring guides
- CLI command reference
- Examples and tutorials
Audience: PRPM end users, package authors, integrators
Project-Level Documentation (root)
Purpose: Standard project files that belong at repository root
Location: Project root /
Files:
README.md- Project overview, quick start, installationCONTRIBUTING.md- Contribution guidelinesCHANGELOG.md- Version history and changesLICENSE- License informationROADMAP.md- Project roadmap and future plans
Audience: Everyone (first impression)
Claude Skills (.claude/skills/)
Purpose: Knowledge base and reference materials for AI assistants
Location: .claude/skills/
Files:
postgres-migrations-skill.md- PostgreSQL migrations guidancepulumi-troubleshooting-skill.md- Pulumi troubleshootingNEW_SKILLS.md- How to create new skillsdocumentation-standards.md- This file
Subdirectories:
prpm-development/- PRPM-specific development knowledgeself-improving/- Self-improvement patternsthoroughness/- Thoroughness and quality guidelines
Audience: AI assistants (Claude, etc.)
Rules for Documentation Placement
When to use development/docs/
✅ GitHub Actions workflows and CI/CD ✅ Internal build/release processes ✅ Development environment setup ✅ Architecture decision records ✅ Internal troubleshooting guides ✅ Database schema documentation ✅ Infrastructure documentation
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.
- 3d ago First seen · 304 lines · 36 tokens per session scan A 9e0dac1ef1bb
documentation-standards is a skill published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,733 once invoked, about $0.0002 per session on Opus 5. 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.
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.
testing-pyramid
Test Distribution Analysis Command 🧪.
dev-workflow
This rule defines the workflow for AI agents to follow when implementing features from user stories, focusing on lean development principles and agile methodologies.
biome
Biome JavaScript/TypeScript linter and formatter.
typescript-standards
TypeScript best practices and coding standards.
git-commit-push
Enforces Git commit standards and conventions when committing and pushing code in Agent Mode. This rule is crucial for keeping track of changes made by agents, and should run whenever the user expresses they want to commit or push code changes made by the agent. This rule should be followed when: 1. the user wants to…