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/ralphgit clone --depth 1 https://github.com/dasomel/oh-my-cursorWhat 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.00013 | $0.00818 |
| Opus 5 | $0.00006 | $0.00409 |
| Sonnet 5 | $0.00003 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
ralph 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ralph Workflow
Ralph is a persistence loop that tracks work via a PRD (Product Requirements Document) and iterates until all stories pass verification.
Triggers
- "ralph", "don't stop", "keep going", "must complete", "until done"
How It Works
1. Create PRD → .omc-cursor/prd.json
2. For each story:
a. Implement (Executor role)
b. Verify (Verifier role)
c. If FAIL → fix and re-verify
3. Repeat until ALL stories pass
4. Final sign-off (Architect role)
Phase 1: PRD Creation
Create .omc-cursor/prd.json with this structure:
{
"title": "Feature/Task Title",
"created": "ISO-8601 timestamp",
"stories": [
{
"id": "S1",
"title": "Story title",
"acceptance": ["criterion 1", "criterion 2"],
"status": "pending",
"attempts": 0
}
],
"status": "in-progress"
}
Phase 2: Story Implementation Loop
For each story with status pending or failed:
Step 1: Implement (Executor Role)
Switching to Executor role.
- Read the story's acceptance criteria
- Implement the minimum code to satisfy ALL criteria
- Run relevant tests
Step 2: Verify (Verifier Role)
Switching to Verifier role.
- Check each acceptance criterion with EVIDENCE
- Run tests → show actual output
- Run build → show actual output
- Update story status in prd.json:
- All criteria met → status: "passed"
- Any criterion failed → status: "failed", increment attempts
Step 3: Fix (if failed)
Switching to Debugger role (if needed) then Executor role.
- Analyze failure
- Fix the issue
- Return to Step 2
Retry Limit
- Max 3 attempts per story
- After 3 failures: mark as "blocked", report to user, move to next story
Phase 3: Final Sign-Off
When all stories are passed:
Switching to Architect role.
- Review overall implementation coherence
- Check for integration issues between stories
- Verify no regression in existing functionality
- Update prd.json status to "complete"
State Management
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.
- 2d ago First seen · 124 lines · 13 tokens per session scan A a6629b88d12e
ralph is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 818 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.
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.