Mistral Rate LimitsSAFE
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Overview
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
4f83675ca38aOBSERVED · 2026-10-09Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: mistral-rate-limits description: >- Control Mistral demand with live workspace limits, token-aware admission, bounded retry, and backpressure. Use when handling throttling or sizing throughput. Trigger with "Mistral rate limits", "fix Mistral 429s", or "design Mistral backpressure". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<workspace> <operation> <latency-slo>" version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: [saas, mistral, reliability] model: inherit effort: high compatibility: "Designed for Claude Code; live or external Mistral actions require network access and explicit approval" --- # Mistral Rate and Backpressure Control ## Overview Treat provider limits as shared workspace capacity, not constants. Admit work against measured demand, preserve deadlines and fairness, and shed load before retry storms consume remaining budget. ## Prerequisites - Current workspace request, token, and spend limits from the Admin Panel. - Per-operation deadline, priority, idempotency, and maximum-attempt policy. - Metrics for admitted, queued, throttled, retried, completed, and abandoned work. ## Current Contract Mistral documents workspace-shared limits across API keys and reports current dimensions in the Admin Panel. Limits vary; never encode a numeric example as a default. ## Authentication Limit telemetry excludes keys, prompts, responses, and files. Admin inspection requires separate authorized identity. ## Instructions 1. Capture current workspace limits and evidence time as observations. 2. Measure demand by operation, model, requests, tokens, and concurrency. 3. Define shared admission buckets and bounded queues with tenant fairness. 4. Honor explicit retry timing; otherwise use capped jitter only for safe transient failures. 5. Stop when deadline, attempt, token, or spend budget ends; return typed overload. 6. Load-test locally, then canary approved traffic and compare queue/SLO evidence. ## Tool Discipline Use Read, Glob, and Grep to inspect code, locks, configuration, tests, and evidence. Use Write and Edit only for approved repository changes. Invocation alone does not authorize network calls, paid usage, uploads, stateful resources, admin mutations, deployments, or deletion. ## Approval Boundaries Require approval for live load, limit increases, capacity changes, or fallback models. Additional keys do not create independent capacity. ## Error Handling - Per-process limiters oversubscribe shared capacity across replicas. - Retries after the user deadline waste tokens and worsen overload. - Fallback changes quality, residency, context, and cost. ## Output Return dated observed limits, demand profile, admission/retry policy, queue bounds, shed behavior, SLO evidence, and rollback. ## Examples - Prioritize interactive work over approved batch preparation. - Return overload once the deadline cannot survive the queue. ## Validation Simulate bursts, replicas, `429`, missing retry metadata, cancellation, deadline expiry, and budget exhaustion offline. Prove that admission resumes gradually after recovery. ## Resources - [Current first-party evidence map](references/official-docs.md) — recheck dated sources before relying on mutable endpoints, models, limits, prices, preview status, or retention. - Record live account observations as environment-specific evidence, not universal Mistral guarantees.
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
4f83675ca38afull audit observations/trust-audit/skill/jeremylongshore__mistral-rate-limits.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-09 | 4f83675ca38a | SAFE | B | 89 | first audit |
Questions
What does the Mistral Rate Limits skill do?
Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.
Is Mistral Rate Limits safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Mistral Rate Limits access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Mistral Rate Limits work with?
Its documentation mentions claude-code. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (4f83675ca38a), read on 2026-10-09. The repository is watched, and a new audit runs when it changes — this is the first audit.