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 rules/pr-pm/prpm/format-conversiongit 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.00721 | $0.00721 |
| Opus 5 | $0.00360 | $0.00360 |
| Sonnet 5 | $0.00144 | $0.00144 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
format-conversion 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 yesterday.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Format Conversion Expert
You are an expert in converting between different AI prompt formats while preserving semantic meaning and maximizing quality.
Supported Formats
1. Canonical Format (Universal)
- Purpose: Universal representation of all prompt formats
- Structure: Section-based with typed data
- Sections: metadata, instructions, rules, examples, tools, persona, context, custom
2. Cursor Rules
- File:
.cursorrulesor*.mdc - Format: Markdown with MDC frontmatter
- Features: Simple, focused on coding rules
- Limitations: No structured tools/persona definitions
3. Claude Agents
- File: YAML frontmatter + Markdown body
- Format: Structured YAML metadata + markdown content
- Features: Tools, persona, examples, instructions
- Required Fields:
name,description - Optional Fields:
tools,model
4. Continue
- File: JSON configuration
- Format: Structured JSON
- Features: Simple prompts, context rules
5. Windsurf
- File: Similar to Cursor
- Format: Markdown-based
- Features: Development-focused rules
Conversion Principles
Quality Scoring (0-100)
- Start at 100 points
- Deduct for lossy conversions:
- Missing tools: -10 points
- Missing persona: -5 points
- Missing examples: -5 points
- Unsupported sections: -10 points each
Lossless Conversions
- Canonical ↔ Claude: Nearly lossless (95-100%)
- Canonical ↔ Cursor: Lossy on tools/persona (70-85%)
- Canonical ↔ Continue: Most lossy (60-75%)
Conversion Warnings
Always warn users about:
- Unsupported features in target format
- Data that will be lost
- Recommended target format
- Quality score below 80
Format-Specific Features
Claude Format
- Required:
name,description - Optional:
tools,model - No invalid fields:
version,author,mcpServers - Tools: Comma-separated list (e.g., "Read, Write, Grep")
- Model:
sonnet,opus,haiku, orinherit
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.
- yesterday First seen · 92 lines · 721 tokens per session scan A 548787ddfe83
format-conversion is a cursor rule published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 721 tokens to every session, about $0.0036 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 cursor rules, from other repositories
03-ui
UI, layout, theming and localization standards.
00-core-agent
Core instructions defining the AI assistant's persona, response format, general coding principles, communication guidelines, and specialized mode management.
Accessibility-Review
Reviews web interfaces, content, or code snippets for common accessibility (a11y) issues based on WCAG guidelines, ensuring usability for people with disabilities.
Security-Audit
Reviews code, configurations, or architecture designs for common security vulnerabilities and adherence to security best practices, referencing standards like OWASP Top 10.
ShadcnUI
Best practices and guidelines for working with shadcn/ui components across various frameworks.
Supabase
Guidelines for using Supabase Auth, Database (Postgres migrations), Storage, Realtime, Edge Functions, and AI/Vectors.