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/exmuzzy/exmuzzy-mcp/cursorrulesgit clone --depth 1 https://github.com/exmuzzy/exmuzzy-mcpWhat 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.01540 | $0.01540 |
| Opus 5 | $0.00770 | $0.00770 |
| Sonnet 5 | $0.00308 | $0.00308 |
| Haiku 4.5 | $0.00154 | $0.00154 |
Grade A, and why
cursorrules 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jira MCP Server - Cursor Rules
Project Overview
Jira Model Context Protocol (MCP) server for Cursor IDE. Provides 31 tools for Jira integration including issue management, board operations, time tracking, and project management.
Key Commands
MCP Command: /jira
When user executes /jira command:
-
WITHOUT parameters - ALWAYS use ONLY
mcp_jira_get_my_issues_grouped()(1 request instead of 6)- Result: All open tasks grouped by status, sorted by priority
- Fastest implementation - 5-6x faster than traditional approach
-
WITH issue key (e.g.,
/jira RIVER-123) - usemcp_jira_get_issue_details()- After displaying issue, suggest quick actions:
- Form execution plan
- Return to author with questions
- Move to progress:
mcp_jira_transition_issue() - Complete:
mcp_jira_transition_issue()ormcp_jira_complete_issue()
- After displaying issue, suggest quick actions:
-
WITH username/surname - Search for user, then show their issues
-
WITH comment -
/jira comment RIVER-123 "text"→mcp_jira_add_comment()
Output Format Requirements
get_my_issues_grouped() Output Rules
-
Status order (by priority)
- В работе (In Progress)
- Сделать (To Do)
- Переоткрыт (Reopened)
- Backlog
- Other statuses...
-
Task sorting within status
- Sort by priority: descending (High → Low)
- Блокер → Highest → High → Medium → Low → Lowest
-
Priority emoji (only for High and above)
- 🔴 Блокер, Highest
- 🟠 High
- ❌ Medium and below: NO emoji
-
Task line format
- With emoji:
- 🔴 **[RIVER-3502]** Full summary text - Without emoji:
- **[RIVER-3790]** Full summary text(3 spaces for alignment) - Summary: FULL TEXT, no truncation
- Only ONE line per task (no additional info rows)
- With emoji:
-
Status header with clickable count
### В работе ([30](URL) задач)- Number links to Jira filtered search for that status
-
Total issues count
**Всего открытых задач**: [176](URL)- Links to all open issues
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 · 194 lines · 1,540 tokens per session scan A 65b913cf05e6
cursorrules is a cursor rule published in the GitHub repository exmuzzy/exmuzzy-mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 1,540 tokens to every session, about $0.0077 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
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
cli-forge-schema
Generate GitHub-compatible Mermaid diagrams — auto-picks diagram type, splits complex ones, converts tables/kanban/PERT.
STAGE_S5_TEST_POINTS
AIDocxWorkFlow Stage 5 — 测试点生成（独立阶段）.
sprint-planning
BMAD BMM Agent: sprint-planning.
head-of-product
Head of Product persona — planning, user stories, UX decisions, scope guardian. Use when discussing product strategy, PRDs, user research, feature proposals, or backlog prioritization.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.