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/zayeagle/omnidev-kitWrote 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/zayeagle/omnidev-kit/01-omnidev-workflow)<a href="https://agentmods.dev/rules/zayeagle/omnidev-kit/01-omnidev-workflow"><img src="https://agentmods.dev/badge/rules/zayeagle/omnidev-kit/01-omnidev-workflow/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/zayeagle/omnidev-kit/01-omnidev-workflow"><img src="https://agentmods.dev/badge/rules/zayeagle/omnidev-kit/01-omnidev-workflow.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.00601 | $0.00601 |
| Opus 5.5 | $0.00240 | $0.00240 |
| Sonnet 5.5 | $0.00120 | $0.00120 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
01-omnidev-workflow 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
OmniDev Trigger Gate (Cursor)
→ Spec: .cursor/skills/od/engine/trigger-gate.md
ACTIVATE
- Signal A: Message starts with
/od(or$od) — includes/od 1…/od 9index pick - Signal A-index: Whole message is bare
1–9and session-log has matchingpending_decision - Not a trigger:
@odskill attach without/od— reference only, do not Phase 0
On activate: Read SKILL.md → engine/activation.md §0–§6 (A-index → §0.1 only). Tool calls first.
DO NOT ACTIVATE
- Normal chat without
/od/$od/ valid bare index - Mid-sentence mentions of
/od …(must be line-start) - Bare
n/ad/continue/y— NOT workflow input - Bare
1–9without diskpending_decision - Do NOT infer OmniDev from prior chat turns alone
If bare n/ad/re/continue or digit-without-pending looks like workflow intent, reply one line only:
⚠️ OmniDev is not active. Use /od 1 (row index), /od n, or /od re.
Advance workflow
| Action | Command |
|---|---|
| Resume | /od re |
| Next phase | /od n |
| Index pick | /od 1…/od 9 or bare 1…9 (with pending) |
| Full autopilot | /od auto / /od al |
| Revise | /od ad |
| End session | /od x |
Phase end: print Handoff (next phase + what to do + /od n + skip /od sk N or "not allowed") then must call AskQuestion when tool exists → UI pick or /od N / bare N / Send command. Autopilot soft-gates skip STOP; hard gates STOP then resume after confirm (board.md §2.5). If tool absent → §8 Markdown table + write pending_decision (forbid box-drawing frames). STOP & WAIT only when actually waiting.
Phase 0 chat: ≤6 lines + Full auto: /od auto hint; details → session-log.
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 · 41 lines · 601 tokens per session scan A 8c56037ebdeb
01-omnidev-workflow is a cursor rule published in the GitHub repository zayeagle/omnidev-kit (4 stars, last pushed 1mo ago), licensed MIT. It adds 601 tokens to every session, about $0.0024 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.