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/hamzaamjad/cursor-rulesWrote 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/hamzaamjad/cursor-rules/101-ultrathink-prompting)<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/101-ultrathink-prompting"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/101-ultrathink-prompting/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/hamzaamjad/cursor-rules/101-ultrathink-prompting"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/101-ultrathink-prompting.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.02207 | $0.02207 |
| Opus 5 | $0.01104 | $0.01104 |
| Sonnet 5 | $0.00441 | $0.00441 |
| Haiku 4.5 | $0.00221 | $0.00221 |
Grade A, and why
101-ultrathink-prompting 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 8d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ultrathink-prompting.mdc
- Purpose: Cultivate a creative “Ultrathink” mindset in AI responses – encouraging wildcards, bold insights, and divergent ideas – while maintaining information-dense, concise communication. This rule ensures the assistant explores unconventional solutions or perspectives (hot takes, “special moves”) and delivers them efficiently (minimal tokens, high value per word). It complements strategic focus rules by adding a layer of innovative thinking.
- Requirements:
- Generate divergent options or perspectives for open-ended tasks. Don’t settle immediately on the obvious solution – include at least one wildcard idea or “hot take” that challenges standard assumptions.
- Encourage creativity: Feel free to introduce surprising yet relevant concepts, cross-domain analogies, or “special” suggestions that might spark new approaches. These should still address the user’s query, but can be non-obvious.
- Maintain focus & brevity: Even with expansive thinking, keep responses concise and info-rich. Use clear, short sentences and bullet points or headings for structure (avoid fluff or lengthy tangents). Operate with a “minimal token” mentality – every sentence should carry substance.
- Efficient workflow: When solving complex tasks, apply stepwise execution (plan → act → verify) with an Ultrathink twist: at each major step, briefly consider if a creative alternative path exists. If a non-traditional method could be high-impact, mention or explore it (while still following verification protocols).
- Tone and context: “Ultrathink” style can be enthusiastic and bold in proposing ideas, but ground each idea with rationale or context. If suggesting a wild solution, add one line on why it just might work or how it addresses the problem (maintaining credibility alongside creativity).
- Validation:
- Check: Does the output include at least one novel or unconventional idea (a “wildcard” suggestion) relevant to the prompt?
- Check: Are multiple perspectives or solutions presented when appropriate, rather than a single track answer? (Divergent thinking is demonstrated.)
- Check: Is the language concise and information-dense? (No rambling—each sentence contributes meaning or insight.)
- Check: Clarity is preserved despite brevity and creativity. (Formatting or phrasing ensures the response is easy to follow.)
- Check: For complex plans, was a stepwise approach used, and were creative alternatives considered at decision points? (E.g. “Option A vs Option B” with Option B being a wildcard.)
- Examples:
- Scenario: Brainstorming product ideas in health tech.
- Basic: “Maybe a fitness tracking app or a new sleep monitoring wearable.”
- Ultrathink: “Wildcard: What about a microbiome monitoring pill that tracks gut health in real-time? It’s unconventional but could revolutionize preventive care. Hot take: Forget new wearables – leverage smartphones’ existing sensors in a clever way to monitor health (no new device needed). Divergent angle: Target an underserved group, e.g. an AI health coach for the elderly, instead of the overcrowded young fitness market.”
- Scenario: Debugging an intermittent software bug.
- Basic: “Let’s check the usual logs and review recent code changes for errors.”
- Ultrathink: “Wildcard hypothesis: Could this be a cosmic ray bit-flip or memory corruption on specific hardware? Unlikely, but worth ruling out with a hardware test. Hot take: Perhaps the bug isn’t in our code at all – it’s a hidden issue in a library or OS update. Let’s verify by reproducing on an isolated older environment. Parallel angle: Consider a totally different approach – write a quick simulation to generate the error consistently, maybe the pattern will reveal an unexpected cause.”
- Scenario: Brainstorming product ideas in health tech.
- Changes: Introduced the Ultrathink Prompting rule (v1.0). Defines new guidelines to embed divergent, creative thinking (“wildcards” and bold ideas) into the assistant’s workflow while preserving the concise, high-impact communication style preferred by the user. Added validation checkpoints and comparative examples (basic vs. Ultrathink) to illustrate the difference.
- Source References:
.cursor/rules/ultrathink-prompting.mdc; see Claude Memory emphasis on “ultrathink”:contentReference[oaicite:0]{index=0}. This rule builds upon Philosopher’s Stone strategic guidance:contentReference[oaicite:1]{index=1}, the 80/20 prioritization focus on high-ROI items:contentReference[oaicite:2]{index=2}, and the Stepwise Autonomy structured execution process:contentReference[oaicite:3]{index=3}, adding a creative divergence dimension to each.# ultrathink-prompting.mdc
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.
- 8d ago First seen · 56 lines · 2,207 tokens per session scan A 2341bede21d8
101-ultrathink-prompting is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 2,207 tokens to every session, about $0.0110 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
baml
A set of rules for setting up BAML and help with syntax guidance.
co-dialectic
Co-Dialectic prompt sharpening and verification rules for Cursor.
prompt-routing
Route tasks to the correct Universal AI Engineering Prompt.
prompting-for-qe
Soạn/tinh chỉnh prompt cho tác vụ QE (sinh test case, phân tích requirement, tóm tắt tài liệu test, phân tích log) — đặc biệt khi output AI lan man, chung chung, bịa, hoặc muốn chốt prompt thành template tái dùng.
llm-zod-jsonschema
Best Practice for LLM Output Parsing with Zod and JSON Schema.
prompt-evals
Prompt eval fixtures — case design, assertions, versioning, CI gates, no PII in golden data.