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.
git clone --depth 1 https://github.com/pr-pm/prpmWrote 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/rules/pr-pm/prpm/creating-skills)<a href="https://agentmods.dev/rules/pr-pm/prpm/creating-skills"><img src="https://agentmods.dev/badge/rules/pr-pm/prpm/creating-skills/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/pr-pm/prpm/creating-skills"><img src="https://agentmods.dev/badge/rules/pr-pm/prpm/creating-skills.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.02458 |
| Opus 5.5 | $0.00008 | $0.00983 |
| Sonnet 5.5 | $0.00004 | $0.00492 |
| Haiku 4.5 | $0.00002 | $0.00246 |
Grade A, and why
creating-skills 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 1mo 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 — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Skills - Meta Guide
Overview
Skills are reference guides for proven techniques, patterns, or tools. Write them to help future Claude instances quickly find and apply effective approaches.
Skills must be discoverable (Claude can find them), scannable (quick to evaluate), and actionable (clear examples).
Core principle: Default assumption is Claude is already very smart. Only add context Claude doesn't already have.
When to Use
Create a skill when:
- Technique wasn't intuitively obvious
- Pattern applies broadly across projects
- You'd reference this again
- Others would benefit
Don't create for:
- One-off solutions specific to single project
- Standard practices well-documented elsewhere
- Project conventions (put those in
.claude/CLAUDE.mdor.cursor/rules)
Required Structure
Frontmatter (YAML)
---
name: skill-name-with-hyphens
description: Use when [triggers/symptoms] - [what it does and how it helps]
tags: relevant-tags
---
Rules:
- Only
nameanddescriptionfields supported (max 1024 chars total) - Name: letters, numbers, hyphens only (no special chars). Use gerund form (verb + -ing)
- Description: Third person, starts with "Use when..."
- Include BOTH triggering conditions AND what skill does
- Match specificity to task complexity (degrees of freedom)
Document Structure
# Skill Name
## Overview
Core principle in 1-2 sentences. What is this?
## When to Use
- Bullet list with symptoms and use cases
- When NOT to use
## Quick Reference
Table or bullets for common operations
## Implementation
Inline code for simple patterns
Link to separate file for heavy reference (100+ lines)
## Common Mistakes
What goes wrong + how to fix
## Real-World Impact (optional)
Concrete results from using this technique
Degrees of Freedom
Match specificity to task complexity:
- High freedom: Flexible tasks requiring judgment
- Use broad guidance, principles, examples
- Let Claude adapt approach to context
- Example: "Use when designing APIs - provides REST principles and patterns"
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.
- 1mo ago First seen · 358 lines · 19 tokens per session scan A b21d61fed9eb
creating-skills is a cursor rule published in the GitHub repository pr-pm/prpm (123 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 2,458 once invoked, about $0.0001 per session on Opus 5.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
llm-integration-rules
A set of rules for connecting an application to a large language model, including Python wrappers, API endpoints, asynchronous calls, retries, and key management.
next-type-llm
Cursor rules for Next.js development with Type LLM integration.
kotlin-springboot-rules
A set of coding rules for Kotlin applications built with Spring Boot, a Java-based framework for web services. It covers project layout, naming, Kotlin style, and common design patterns.
fastapi-file-structure
A recommended FastAPI project structure that separates routes, configuration, security, database sessions, create/read/update/delete operations, models, and schemas into modules.
fastapi-dependency-injection
Guidelines for using dependency injection in FastAPI. Dependency injection lets a function receive services such as database sessions, settings, or the current user instead of creating them itself.
fastapi-startup-and-shutdown-events
Rules for running setup tasks when a FastAPI application starts and cleanup tasks when it stops, such as opening database connections, loading configuration, or starting background tasks.