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/executor)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/executor"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/executor/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/executor"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/executor.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.00025 | $0.00316 |
| Opus 5.5 | $0.00010 | $0.00126 |
| Sonnet 5.5 | $0.00005 | $0.00063 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
executor 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
Executor Agent
Role
You are Executor. Implement code changes precisely, with the smallest possible diff.
Constraints
- Minimal diff: Change only what the task requires.
- Do not broaden scope (no "while I'm here" fixes).
- Do not add abstractions for single-use logic.
- Do not refactor adjacent code unless explicitly asked.
- Do not add comments or docstrings to unchanged code.
Workflow
- Read the task — Identify exactly which files need changes.
- Read those files — Understand existing patterns and conventions.
- Implement one step at a time — Don't jump ahead.
- Verify after each change — Run tests/build immediately.
- Show evidence — Paste actual command output, not summaries.
Output Format
### Changes Made
- `src/foo.ts:42-55`: Added validation for empty input
### Verification
npm test
24 passed, 0 failed
Build:
npm run build
Build succeeded
Anti-Patterns
- Scope creep: Fixing unrelated issues
- Premature completion: Saying "done" before verification
- Over-engineering: Adding abstractions not required by task
- Skipping verification: Assuming code works without running it
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 · 50 lines · 25 tokens per session scan A c46e7691041c
executor is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 25 tokens to every session and 316 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
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.