Mistral Cost TuningSAFE
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-cost-tuning description: >- Control Mistral spend with live account rates, usage attribution, admission budgets, and quality-preserving experiments. Use when forecasting or reducing cost. Trigger with "optimize Mistral cost", "set a Mistral budget", or "explain Mistral spend". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<workspace> <workload> <budget-period>" version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: [saas, mistral, cost] model: inherit effort: high compatibility: "Designed for Claude Code; live or external Mistral actions require network access and explicit approval" --- # Mistral Spend and Usage Governance ## Overview Turn spend into an attributable operating signal. Use live billing/model evidence, distinguish attempted from completed work, and require quality and safety evaluation before workflow changes. ## Prerequisites - Authorized billing/usage evidence with observation time. - Operation-level usage, retry, caching, and business-outcome metrics. - A spend owner, budget period, alerts, and evaluation set. ## Current Contract Billing, model rates, and workspace limits vary by plan and time. Do not hard-code a price table, context size, batch discount, or model recommendation. ## Authentication Billing review uses an authorized admin session; inference uses the server-side key. Receipts exclude credentials, prompts, responses, invoices, and personal billing details. ## Instructions 1. Capture current rates, feature charges, usage, caps, and evidence times from authorized views. 2. Attribute requests, tokens, retries, files, batch, OCR, audio, and stateful work to operations. 3. Calculate unit cost and waste from retries, abandonment, excessive context, and duplicates. 4. Prioritize admission budgets, request bounds, deduplication, and scheduling. 5. Evaluate model, batch, or routing changes against the same correctness and safety set. 6. Alert on cap approach, cap reached, invoice failure, and unattributed use with fail-safe behavior. ## 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 Spend-cap changes, purchases, model/endpoint substitution, batch conversion, and production routing require approval. Never raise a cap automatically. ## Error Handling - Lower unit price can raise total spend through output, retry, or failure changes. - Batch economics and eligibility must be rechecked. - Unattributed usage is an incident signal. ## Output Return dated rates and limits, attribution, unit economics, waste, evaluated options, controls, owner, and rollback. Separate observed facts from forecasts and assumptions. ## Examples - Reduce duplicate retries before evaluating a cheaper model. - Alert on forecast budget crossing while preserving admission bounds. ## Validation Reconcile provider totals to app attribution, sample retry accounting, test cap-reached behavior, and preserve quality/safety/tenancy. ## 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-cost-tuning.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 Cost Tuning 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 Cost Tuning 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 Cost Tuning access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Mistral Cost Tuning 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.