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/madebyaris/rakitui-ai/cursor-tools-masterygit clone --depth 1 https://github.com/madebyaris/rakitui-aiWrote 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/madebyaris/rakitui-ai/cursor-tools-mastery)<a href="https://agentmods.dev/rules/madebyaris/rakitui-ai/cursor-tools-mastery"><img src="https://agentmods.dev/badge/rules/madebyaris/rakitui-ai/cursor-tools-mastery.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 | $0.03584 | $0.03584 |
| Opus 5 | $0.01792 | $0.01792 |
| Sonnet 5 | $0.00717 | $0.00717 |
| Haiku 4.5 | $0.00358 | $0.00358 |
Grade A, and why
cursor-tools-mastery 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 5d 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 — 623 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor 2.2 Tools Mastery
Complete reference for all Cursor IDE tools. Use these tools effectively to accomplish tasks efficiently.
CRITICAL: Agentic-First Tool Usage
The Golden Rule: Verify Before You Act
Every action follows this pattern:
- CHECK - What exists? What's the current state?
- VERIFY - What versions? What's available?
- ACT - Make the change using proper tools
- VALIDATE - Did it work? Any errors?
Pre-Action Verification Protocol
Before ANY significant action:
BEFORE CREATING PROJECT:
1. Check if CLI tool exists: run_terminal_cmd("which flutter")
2. Check CLI version: run_terminal_cmd("flutter --version")
3. Web search for current version: web_search("Flutter stable December 2024")
4. Check if project already exists: list_dir("./")
BEFORE INSTALLING PACKAGES:
1. Check package.json/pubspec.yaml exists: read_file("package.json")
2. Check if already installed: read_file("package-lock.json")
3. Verify package name/version: web_search("lodash npm latest version")
BEFORE EDITING CODE:
1. Read the file first: read_file("src/component.tsx")
2. Understand context and dependencies
3. Check for related files that might need updating
Proactive Web Search Usage
ALWAYS use web_search for:
- Package versions before installing
- Framework syntax when unsure
- Error messages you encounter
- API documentation verification
- Current best practices
Search Pattern:
web_search("[package/framework] [specific feature] [current year/month]")
Examples:
web_search("Next.js 15 App Router server actions December 2024")web_search("React 19 useFormStatus hook syntax")web_search("shadcn ui button component installation")
Search Tools
read_file
Purpose: Read file contents with line numbers
When to Use:
- Examining specific files
- Understanding code structure
- Reviewing implementations
- Checking configurations
Best Practices:
- Read whole files unless very large (>1000 lines)
- Use
offsetandlimitfor large files - Batch multiple file reads in parallel
- Check imports and dependencies
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.
- 5d ago First seen · 623 lines · 3,584 tokens per session scan A ed36f8cc6699
cursor-tools-mastery is a cursor rule published in the GitHub repository madebyaris/rakitui-ai (5 stars, last pushed 7mo ago), licensed MIT. It adds 3,584 tokens to every session, about $0.0179 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-31.
Other cursor rules, from other repositories
AIRules
NexusLink MCP four-step workflow and prohibitions (copy to project .cursor/rules/ and fill the project-specific section).
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
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.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.