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/madebyaris/advance-minimax-m3-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/madebyaris/advance-minimax-m3-cursor-rules/clarify-first-prompting)<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/clarify-first-prompting"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/clarify-first-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/madebyaris/advance-minimax-m3-cursor-rules/clarify-first-prompting"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/clarify-first-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.00020 | $0.00351 |
| Opus 5 | $0.00010 | $0.00176 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
clarify-first-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 12d 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
Clarify-First Prompting
Clarification is for real uncertainty, not for information the repo or runtime already contains.
Inspect Before Asking
Before asking a question, first check whether the answer is available through:
- project files
- existing code patterns
- tool output
- current docs when version-sensitive behavior matters
Do not ask the user for information you can inspect directly.
When to Ask
Ask only when the answer materially changes the implementation:
- security or authentication model
- destructive data or migration strategy
- major architecture branch
- user-facing product choice with costly reversal
When to Proceed
Proceed without asking when:
- project conventions already answer the question
- the choice is small and reversible
- a safe default exists
- the user explicitly asked for a best-effort implementation
Question Rules
- Ask at most 1-2 critical questions at a time.
- Use structured questions only when the choice has real tradeoffs.
- Put the recommended or safest default first when presenting options.
- Once the user answers, proceed without re-confirming.
Good Pattern
1. Inspect repo and runtime
2. Identify the true unknown
3. Ask only if that unknown changes the architecture or outcome
4. Otherwise choose a safe default and continue
Anti-Patterns
Do not:
- ask about framework, package, or file structure when the repo can answer it
- ask about tiny implementation details
- repeat questions the user already answered
- use fake
<think>or<thinking>blocks as clarification scaffolding
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.
- 12d ago First seen · 59 lines · 20 tokens per session scan A 39c128316aab
clarify-first-prompting is a cursor rule published in the GitHub repository madebyaris/advance-minimax-m3-cursor-rules (125 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 351 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-30.
Other cursor rules, from other repositories
git-commit
Use this when the user asks for a git commit, commit message, or commit command.
learnship
Activate learnship agentic engineering workflows — structured phases, persistent memory, learning partner, and impeccable UI design. Use whenever a user is working on a software project or asks about project planning, phases, workflows, or how to build something.
behavior-principles
Global behavioral principles for all AI-assisted work in this repository. Covers thinking before coding, simplicity, surgical changes, goal-driven execution, and communication standards.
coding
Core coding behavior for this repository. Always prefer cautious, minimal, reversible changes.
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.
java-spring
Optional Spring Boot example-pack coding rules. Apply only when editing an adopted project or spring-boot profile output.