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/Jkudjo/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/jkudjo/oh-my-cursor/qa)<a href="https://agentmods.dev/rules/jkudjo/oh-my-cursor/qa"><img src="https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/qa/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/jkudjo/oh-my-cursor/qa"><img src="https://agentmods.dev/badge/rules/jkudjo/oh-my-cursor/qa.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.00596 |
| Opus 5.5 | $0.00007 | $0.00238 |
| Sonnet 5.5 | $0.00003 | $0.00119 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
qa 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 1mo 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@qa
Trigger: After implementing a feature, before shipping, or when tests are failing.
Modes
| Flag | Behavior |
|---|---|
--tests (default) |
Run test suite and cycle until passing |
--build |
Run build and cycle until it succeeds |
--lint |
Run lint and cycle until clean |
--typecheck |
Run type check and cycle until clean |
--full |
Run all: typecheck → lint → build → tests |
--report |
Report only, no fixes |
Max cycles: 5. After 5 failed cycles, stop and report remaining issues.
Cycle Protocol
Per Cycle:
-
Run — execute the relevant command(s) for the selected mode.
-
Check — did it pass?
- YES → exit with success summary
- NO → continue to diagnose
-
Diagnose — analyze the failure output:
- What failed and why (root cause, not just symptoms)
- Which files/lines are involved
- Is this a real failure or a test environment issue?
-
Fix — apply the minimum fix to resolve the root cause:
- One root cause at a time
- Verify the fix makes sense before applying
- Never break passing tests to fix failing ones
-
Repeat — go back to step 1 with updated iteration count.
-
Call
update_mode_stateafter each cycle withphase="cycle-N"anditeration=N.
Exit Conditions
| Condition | Action |
|---|---|
| All checks pass | Report: PASS, N cycles used |
| Max cycles (5) reached | Report: FAIL, list remaining issues |
| Unfixable issue (env/config) | Report: BLOCKED, describe blocker |
Final Report
## QA Report: {scope}
**Result:** PASS | FAIL | BLOCKED
**Cycles used:** N/5
**Mode:** {flags}
### Issues fixed
1. `file:line` — description of fix
### Remaining issues (if FAIL)
1. `file:line` — description, repro steps
### Health score: XX/100
(−25 per critical bug, −10 per major, −3 per minor)
Call save_artifact type=specs, slug=qa-{scope-slug}, content=the report.
Call set_memory key=last-qa, value=the report.
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.
- 1mo ago First seen · 83 lines · 17 tokens per session scan A bd72481e3a14
qa is a cursor rule published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 596 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
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
testing
Testing: test design, mocking strategy, coverage philosophy.
jest
Jest: describe/it, matchers, mocking, async testing.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
vitest
Vitest: unit testing, mocking, coverage, snapshot testing.
cypress
Cypress: cy commands, selectors, fixtures, intercepts.