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-verification)<a href="https://agentmods.dev/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-m3-verification"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-m3-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-verification"><img src="https://agentmods.dev/badge/rules/madebyaris/advance-minimax-m3-cursor-rules/minimax-m3-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.00026 | $0.00853 |
| Opus 5 | $0.00013 | $0.00426 |
| Sonnet 5 | $0.00005 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
minimax-m3-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 11d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
M3 Verification Playbook
Extends the always-on minimax-m3-status-verification contract with check selection, shell/browser guidance, multimodal-grounded checks, and self-review. The status labels, minimum proof table, and closeout shape live in that always-on rule — do not restate them here.
Proof Selection
- Match the proof to the claim being made.
- Prefer the smallest proof that can honestly support the user-facing claim.
- Strengthen the proof when the claim involves runtime behavior, interaction, styling, navigation, persistence, or integration.
- If the deliverable promises a styling or toolchain layer (Tailwind, shadcn, routing, persistence), verify that layer directly — do not assume the scaffold wired it correctly.
- Visual / design / styling claim →
multimodal-grounded: read the attached image/frame, name the file path, name the region inspected, and check the relevant region. Do not infer from prose or from a memory of the pre-change state. See theminimax-m3-multimodal-inputskill for the full workflow. - Bug fix → red → green: reproduce the failure with an exact check before fixing, then re-run that same check after. A check that was never red proves the wrong thing.
Test Integrity During Verification
A passing check only counts as proof if the check itself was not bent:
- Never delete, skip, loosen, widen tolerances on, or special-case a test to reach green. If the test looks wrong, present the evidence to the user — changing the spec is their call.
- A new test must be able to fail: confirm it fails against the pre-fix code (or would, by construction) before counting it as proof.
- Hardcoding the expected output into production code, or branching on test-only inputs, is claim-gaming — treat the work as
blocked, notverified.
Shell-Based Checks
Use the smallest useful command first. Prefer the repo's own scripts and CI entrypoints when they exist (see core Code Discipline).
- JavaScript/TypeScript:
lint,typecheck,build, targeted tests, focused scripts - Python:
ruff, targetedpytest, import or compile checks - Go:
go build,go test,go vet - Rust:
cargo check,cargo test,cargo clippy - Flutter:
flutter analyze,flutter test - Swift:
swift build,swift test,xcodebuildwhen applicable
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.
- 11d ago First seen · 77 lines · 26 tokens per session scan A 78e51aca8905
minimax-m3-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 26 tokens to every session and 853 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
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…
testing
Optional Spring Boot example-pack testing rules. Apply only when editing an adopted project or spring-boot profile output.
debugging
Use this when debugging failures, broken tests, runtime errors, or unexpected behavior.
chaos
Failure injection mode — stress test implementations by simulating failures and hostile conditions.
performance
Performance: profiling-first optimization, caching, bottleneck patterns.
testing
Testing: test design, mocking strategy, coverage philosophy.