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/deslicer/mcp-for-splunk/cursorrulesgit clone --depth 1 https://github.com/deslicer/mcp-for-splunkWhat 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.00756 | $0.00756 |
| Opus 5 | $0.00378 | $0.00378 |
| Sonnet 5 | $0.00151 | $0.00151 |
| Haiku 4.5 | $0.00076 | $0.00076 |
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 2d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Rules for MCP Server for Splunk
README and Markdown Standards
When editing any *.md file, apply these standards:
README Writing Guidelines
- Follow the guide in
docs/readme-guide.mdfor all README files - Use the 3-Layer Principle: Hook (10s) → Quick Start (2m) → Navigation (30s)
- Target audience first: Define personas and technical level before writing
- Maximum 1200 words for main READMEs, focus on navigation to detailed docs
Markdown Formatting Rules
# H1: Document title only (one per file)
## H2: Major sections
### H3: Subsections (use sparingly, avoid H4+)
**Bold**: Important terms, actions, key concepts
*Italic*: Emphasis, file names, variables
`Code`: Commands, file paths, configuration values
Content Standards
- Paragraphs: Maximum 3-4 sentences
- Code blocks: Always include language for syntax highlighting
- Links: Use descriptive text, prefer relative paths for internal links
- Images: Include alt text, optimize for <500KB, use repo-relative paths
- Lists: Use parallel structure, start with action verbs when possible
Code Example Requirements
- Test all code examples before including
- Include expected output when helpful
- Show command context (directory, prerequisites)
- Comment complex commands
- Use realistic examples, not
foo/barplaceholders
README Structure Enforcement
For main README files, ensure these sections exist:
- Hero Section: Title, badges, value proposition, key features
- Quick Start: Prerequisites, installation, first success
- Documentation Hub: Links to detailed guides
- Community/Support: Issues, discussions, help channels
Writing Style Rules
- Use active voice: "Run the command" not "The command should be run"
- Be specific: "Takes 2 minutes" not "Quick setup"
- Show outcomes: "You'll see X" not "The system will do Y"
- Use direct address: "You" instead of "users" or "developers"
- Avoid jargon without explanation
Quality Checks
Before saving any .md file:
- All links work and point to correct locations
- Code examples are tested and current
- Images load and have alt text
- Headings follow logical hierarchy
- Content serves the target audience
- Length appropriate for document type
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.
- 2d ago First seen · 86 lines · 756 tokens per session scan A ec95f1a08e41
cursorrules is a cursor rule published in the GitHub repository deslicer/mcp-for-splunk (27 stars, last pushed 8d ago), licensed Apache-2.0. It adds 756 tokens to every session, about $0.0038 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 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.