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/creating-claude-commands)<a href="https://agentmods.dev/skills/pr-pm/prpm/creating-claude-commands"><img src="https://agentmods.dev/badge/skills/pr-pm/prpm/creating-claude-commands.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.00025 | $0.03725 |
| Opus 5 | $0.00013 | $0.01862 |
| Sonnet 5 | $0.00005 | $0.00745 |
| Haiku 4.5 | $0.00003 | $0.00373 |
Grade A, and why
creating-claude-commands 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 8d 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 — 745 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Claude Code Slash Commands
Expert guidance for creating Claude Code slash commands - quick actions triggered by /command-name.
When to Use This Skill
Activate this skill when:
- User wants to create a new slash command
- User needs to understand slash command structure
- User asks about frontmatter fields for commands
- User wants validation guidance for commands
- User needs examples of command patterns
Quick Reference
| Field | Required | Type | Description |
|---|---|---|---|
description |
No | string | Brief description shown in autocomplete |
allowed-tools |
No | string | Comma-separated list of tools (inherits if not specified) |
argument-hint |
No | string | Expected arguments (e.g., add [tagId] | remove [tagId] | list) |
model |
No | string | Specific model (sonnet, opus, haiku, inherit) |
disable-model-invocation |
No | boolean | Prevent SlashCommand tool from calling this |
commandType |
No | string | Set to "slash-command" for round-trip conversion |
Special Features
File Referencing with @
Reference files directly in command prompts using @ prefix:
Review the implementation in @src/utils/helpers.js
Compare @src/old-version.js with @src/new-version.js
Bash Execution with !
Execute bash commands inline using ! prefix (requires Bash in allowed-tools):
---
allowed-tools: Bash(git *)
---
Current git status: !`git status`
Last 5 commits: !`git log --oneline -5`
Arguments
$ARGUMENTS- All arguments passed to command$1,$2,$3...$9- Individual positional arguments
Namespacing
- Use subdirectories in
.claude/commands/to organize commands - Commands appear as
/subdirectory.command-name - Example:
.claude/commands/git/quick-commit.md→/git.quick-commit
File Location
Slash commands must be saved as Markdown files:
Project commands (shared with team):
.claude/commands/command-name.md
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.
- 8d ago First seen · 745 lines · 25 tokens per session scan A db798e0980de
creating-claude-commands is a skill published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 3,725 once invoked, about $0.0001 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.
biome
Biome JavaScript/TypeScript linter and formatter.
nextjs-react19
Next.js with React 19 App Router patterns.
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…
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…
android-upgrade
Workflow for changing an existing working Android project — upgrading dependencies, AGP/Gradle or SDK levels, migrating deprecated APIs, refactoring, and fixing bugs, without breaking what already works. Covers baseline verification, scoping the diff, targetSdk behaviour changes, SharedPreferences/Room data…