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/minimax-m3-status-verification)<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-m3-status-verification"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-m3-status-verification/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/minimax-m3-status-verification"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-m3-status-verification.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.01031 | $0.01031 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
minimax-m3-status-verification 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MiniMax M3 Status And Verification
Code is not done until it has been proved at the surface the user cares about.
Allowed Status Labels
Use explicit status language in updates and closeouts:
changed: you edited or produced somethingverified: you proved a claim with a relevant checkunverified: the work exists but the required proof was not runblocked: required progress or proof failed and the task cannot honestly be called doneassumption: a choice or statement depends on inference rather than direct evidencemultimodal-grounded: the claim is grounded in an attached image, video frame, screenshot, or design mock that was actually read in the current session (M3 native multimodal input). Use this for visual-fidelity claims; name the file path and the region inspected.
Do not use done, fixed, working, or resolved without naming the proof immediately after.
Claim And Evidence Rules
- Match the proof to the strongest claim you make.
- Name the exact evidence for completion claims.
- Separate what you observed from what you infer.
- If intended verification failed and you fall back to a weaker check, say so explicitly.
- If a required check was not run, say
implemented but unverifiedand list the missing proof. - For visual claims, prefer
multimodal-grounded(read the actual frame) oververifiedinferred from code-only reading. If you claim the UI looks right without re-reading the post-change state, that is notverified.
Minimum Proof By Change Type
| Change type | Minimum proof |
|---|---|
| Localized edit | Re-read or one targeted static check |
| Bug fix | Red → green: the reproduction fails before the change and passes after; green → green proves nothing |
| Backend, logic, or API change | Targeted test, command, script, or runtime request |
| UI or interaction change | Browser or user-surface verification, plus static checks as needed |
| Integration-sensitive change | Build or typecheck plus one focused behavior check |
| Visual / design / styling claim | multimodal-grounded: read the attached screenshot/frame, name the file path, name the region inspected, and (when applicable) state "visually diffed against pre-change" or "not visually diffed" |
| New app or scaffold | Setup/install succeeds, startup or health check succeeds, production build succeeds, one primary happy-path flow works, and any promised persistence or reload behavior is verified |
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 · 87 lines · 1,031 tokens per session scan A 32d1269d3dc2
minimax-m3-status-verification 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 1,031 tokens to every session, about $0.0052 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
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.
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.