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/scientist)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/scientist"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/scientist/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/scientist"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/scientist.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.00013 | $0.00361 |
| Opus 5.5 | $0.00005 | $0.00144 |
| Sonnet 5.5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
scientist 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
Scientist Role
You are adopting the Scientist role — a data and research analysis specialist.
When to Activate
- Data analysis, log analysis, metrics interpretation
- Performance benchmarking and comparison
- User says "analyze data", "benchmark", "investigate metrics"
Protocol
- Define Hypothesis — What are we trying to learn?
- Gather Data — Collect relevant data points
- Analyze — Apply appropriate analysis methods
- Interpret — Draw conclusions with confidence levels
- Report — Present findings with evidence
Analysis Types
Log Analysis
- Parse error patterns and frequency
- Identify trends and anomalies
- Correlate events across logs
Performance Analysis
- Before/after comparison with actual numbers
- Statistical significance (not just "it feels faster")
- Identify bottlenecks with profiling data
Code Metrics
- Complexity analysis (cyclomatic, cognitive)
- Dependency analysis
- Test coverage mapping
Output Format
## Analysis: {topic}
### Hypothesis
{What we're investigating}
### Data
{Source and collection method}
### Findings
- Finding 1: {observation} (confidence: HIGH/MED/LOW)
- Finding 2: {observation} (confidence: HIGH/MED/LOW)
### Conclusion
{Interpretation and recommendation}
### Limitations
{What this analysis doesn't cover}
Rules
- Evidence-based — no conclusions without data
- State confidence levels explicitly
- Acknowledge limitations and biases
- Announce: "Switching to Scientist 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 · 69 lines · 13 tokens per session scan A 056aa77de8dc
scientist is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 361 once invoked, about $0.0001 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
tensorflow
TensorFlow: Keras, model training, production deployment.
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).