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/dasomel/oh-my-cursor/autopilotgit 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/autopilot)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/autopilot"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/autopilot.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00417 |
| Opus 5 | $0.00019 | $0.00209 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
autopilot 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 3d 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
Autopilot Workflow
Trigger Conditions
Activate when user says: "autopilot", "build me", "create me", "full auto", "autonomous"
Execution Phases
Phase 0: Expansion
[Switching to Analyst role]
- Extract requirements from user's description
- Clarify ambiguities (ask ONE question if critical info is missing)
- Write spec to
.omc-cursor/spec.md
Phase 1: Planning
[Switching to Planner role]
- Read
.omc-cursor/spec.md - Create implementation plan in
.omc-cursor/plans/impl.md - Include: steps, acceptance criteria, files to change
Phase 2: Implementation
[Switching to Executor role]
- Read plan from
.omc-cursor/plans/impl.md - Implement step by step
- Verify after each step
Phase 3: QA Loop (max 5 cycles)
Run tests → Any failures?
YES → [Debugger role] Fix → Repeat
NO → Continue to Phase 4
After 3 same-error cycles: STOP and report fundamental blocker.
Phase 4: Self-Review
[Switching to Reviewer role] — Code quality check [Switching to Security Reviewer role] — Vulnerability scan Fix any 🔴 CRITICAL findings, then re-verify.
Completion Criteria
- All tests pass (show output)
- Build succeeds (show output)
- No 🔴 CRITICAL review findings
- Acceptance criteria in spec all checked off
State Files
.omc-cursor/spec.md— Requirements.omc-cursor/plans/impl.md— Implementation plan.omc-cursor/notepad.md— Session notes
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.
- 3d ago First seen · 54 lines · 38 tokens per session scan A 181db2a49d79
autopilot is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 417 once invoked, about $0.0002 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.
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.