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 skills add Jkudjo/oh-my-cursor --skill diagnosegit 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/skills/jkudjo/oh-my-cursor/diagnose)<a href="https://agentmods.dev/skills/jkudjo/oh-my-cursor/diagnose"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-cursor/diagnose/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/skills/jkudjo/oh-my-cursor/diagnose"><img src="https://agentmods.dev/badge/skills/jkudjo/oh-my-cursor/diagnose.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.00265 |
| Opus 5 | $0.00009 | $0.00133 |
| Sonnet 5 | $0.00003 | $0.00053 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
diagnose 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 9d 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
diagnose
Structured diagnosis that prevents tunneling on the first plausible theory.
The iron law
Root cause before fix. Never propose a solution without evidence-backed cause.
What it does
- Gathers facts — what, when, scope, what changed (read-only)
- Generates ≥5 hypotheses across app/data/network/infra/client domains — before investigating any
- Ranks by likelihood × blast radius × ease of ruling out
- Investigates in ranked order, updating confidence as evidence comes in
- Produces a confirmed diagnosis with blast radius, rollback path, and verification steps
- Hands off to
@ralphfor the fix
When to use
- "The API is returning 500s"
- "Users report X but metrics look fine"
- "It works in staging but not prod"
- Any situation where the cause is unknown
What it avoids
- Tunneling on the first theory
- Treating "check the logs" as a hypothesis
- Trusting green dashboards as proof of no incident
- Fixing before the root cause is confirmed
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.
- 9d ago First seen · 33 lines · 17 tokens per session scan A 55af1988d1a5
diagnose is a skill published in the GitHub repository Jkudjo/oh-my-cursor (1 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 265 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 skills, from other repositories
systematic-debugging
Use when encountering bugs, test failures, unexpected behavior, or any technical issue before proposing fixes.
firebase-crashlytics
Use when implementing crash reporting, capturing fatal/non-fatal errors, recording isolate/async exceptions, customizing reports, or uploading obfuscated symbols.
flutter-errors
Use when hitting layout errors (RenderFlex overflow, unbounded constraints, RenderBox not laid out), scroll errors, or setState-during-build errors.
cause-and-effect
Systematic Fishbone analysis exploring problem causes across six categories.
why
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals.
audit-performance
Audit runtime performance (CWV, load priority). Use when "slow page", "LCP/INP/CLS", "fetchpriority", "early hints", "speculation rules", "bfcache", or "long tasks". JS payload → audit-bundle-size. Instant nav implement → enhance-web-instant-nav. Breaking point → test-load.