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/roy2392/vibe-agents-rules/create-commandgit clone --depth 1 https://github.com/roy2392/vibe-agents-rulesWhat 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.00410 | $0.00410 |
| Opus 5 | $0.00205 | $0.00205 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
create-command 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.
This is a copy
100% identical to create-command — 0 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.
What it actually says
Create Command
Guide for creating new custom Claude commands with proper structure.
Process:
1. Understanding Purpose
- What problem does this command solve?
- Who will use this command?
- What is the expected output?
- How will users interact with it?
2. Category Classification
Determine command type:
- Planning: Project setup, architecture decisions
- Implementation: Code generation, feature development
- Analysis: Code review, performance analysis
- Testing: Test creation, validation
- Documentation: Docs generation, updates
- Workflow: Multi-step processes
- Utility: Helper commands, tools
3. Pattern Selection
Study similar existing commands:
- Analyze structure and flow
- Note common patterns
- Identify reusable components
- Follow established conventions
4. Command Location
Choose appropriate location:
- Project-specific:
.claude/commands/ - User-level:
~/.claude/commands/ - Consider reusability and context
5. Command Structure
Create with these sections:
- Title: Clear, action-oriented name
- Description: One-line summary
- Usage: How to invoke with parameters
- Process: Step-by-step instructions
- Examples: Concrete usage examples
- Output: Expected results
- Notes: Special considerations
Template:
# Command Name
Brief description of what this command does.
## Usage:
`/command-name [arguments]`
## Process:
1. First step
2. Second step
3. Third step
## Examples:
- Example 1
- Example 2
## Notes:
- Important considerations
- Limitations
Best Practices:
- Keep commands focused and single-purpose
- Include parameter validation
- Provide helpful error messages
- Document expected inputs/outputs
- Consider edge cases
- Test thoroughly before finalizing
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 · 75 lines · 410 tokens per session scan A 2823d7dfaeb5
create-command is a cursor rule published in the GitHub repository roy2392/vibe-agents-rules (11 stars, last pushed 1y ago), licensed MIT. It adds 410 tokens to every session, about $0.0020 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to create-command, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.