executor

A set of rules for an executor agent that implements one clearly defined code change with a small, focused edit. It also requires verification and reporting of the actual results.

In plain words
What is it for?
Use it to read the relevant files, make the planned change, run tests or builds, and report the files changed and evidence of success.
Why use it?
It keeps implementation work within the approved scope and reduces unrelated changes or unverified claims.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/dasomel/oh-my-cursor/executor
Clone the repo
git clone --depth 1 https://github.com/dasomel/oh-my-cursor
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 316 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00316
Opus 5 $0.00013 $0.00158
Sonnet 5 $0.00005 $0.00063
Haiku 4.5 $0.00003 $0.00032

Measured yesterday against content hash c46e7691041c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

rules/agents/executor.mdc · 50 lines

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

  1. Read the task — Identify exactly which files need changes.
  2. Read those files — Understand existing patterns and conventions.
  3. Implement one step at a time — Don't jump ahead.
  4. Verify after each change — Run tests/build immediately.
  5. 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
Changes

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.

  1. yesterday First seen · 50 lines · 25 tokens per session scan A c46e7691041c

Subscribe to this mod's changes

executor is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 316 once invoked, about $0.0001 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.