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/ultraqa)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/ultraqa"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/ultraqa/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/ultraqa"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/ultraqa.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.00017 | $0.00447 |
| Opus 5.5 | $0.00007 | $0.00179 |
| Sonnet 5.5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
ultraqa 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
UltraQA Workflow
Relentless QA cycling — test, verify, fix, repeat until the goal is fully met.
Trigger Keywords
"ultraqa", "qa loop", "keep testing until it works"
Process
Cycle 1:
1. [QA Tester] → Run all tests, check build, verify behavior
2. [QA Tester] → Report failures with evidence
3. [Debugger] → Diagnose root cause of each failure
4. [Executor] → Fix each issue (minimal diff)
5. [Verifier] → Confirm fix works, no regressions
If failures remain → next cycle
Cycle N (max 5):
Repeat steps 1-5
Final:
[Verifier] → Full verification report
Exit Conditions
- Success: All tests pass, build succeeds, no regressions
- Max cycles: After 5 cycles, report remaining issues to user
- Blocked: Same failure persists after 3 fix attempts → escalate to user
Cycle Report
Each cycle appends to .omc-cursor/qa-report.md:
## Cycle {N}
### Tests Run
- Total: {count}, Passed: {count}, Failed: {count}
### Failures
| Test | Error | Root Cause | Fix Applied | Status |
|------|-------|-----------|-------------|--------|
| {test} | {error} | {cause} | {fix} | FIXED/OPEN |
### Build Status: PASS/FAIL
### Regressions: NONE / {list}
Rules
- Always show actual test output, not summaries
- Fix one issue at a time to isolate changes
- Run full test suite after each fix, not just the failing test
- Never skip a failing test — fix it or explain why it can't be fixed
- Announce: "UltraQA Cycle {N}: Running full test suite."
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 · 65 lines · 17 tokens per session scan A 60ed481c6469
ultraqa is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (3 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 447 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
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.