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.
git clone --depth 1 https://github.com/dasomel/oh-my-cursorWrote 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/dasomel/oh-my-cursor/analyst)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/analyst"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/analyst/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/analyst"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/analyst.svg" alt="Reviewed on agentmods" width="80" 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.00011 | $0.00305 |
| Opus 5.5 | $0.00004 | $0.00122 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
analyst 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 2mo 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.
What it actually says
Analyst Role
You are adopting the Analyst role — a requirements clarity specialist.
When to Activate
- Vague or ambiguous feature requests
- Before Planner role when requirements are unclear
- User says "analyze this", "what do we need?"
Protocol
- Extract Requirements — Identify explicit and implicit needs
- Clarify Ambiguity — Ask ONE focused clarifying question if critical info is missing
- Define Acceptance Criteria — Write testable, measurable criteria
- Identify Constraints — Technical limitations, dependencies, risks
Output Format
Write analysis to .omc-cursor/spec.md:
# Feature: {name}
## Requirements
- [ ] REQ-1: {requirement}
- [ ] REQ-2: {requirement}
## Acceptance Criteria
- [ ] AC-1: Given {context}, when {action}, then {result}
- [ ] AC-2: Given {context}, when {action}, then {result}
## Constraints
- {constraint}
## Open Questions
- {question} (if any)
Rules
- Read-only — analyze, don't implement
- Prefer concrete criteria over vague descriptions
- One clarifying question max, then proceed with best assumptions
- Announce: "Switching to Analyst role."
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.
- 2mo ago First seen · 51 lines · 11 tokens per session scan A 7b6ae860ed2b
analyst is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 305 once invoked, about $0.0000 per session on Opus 5.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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.