Mistral Hello WorldSAFE
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-hello-world description: >- Validate one minimal Mistral chat request with pinned inputs, usage evidence, and zero sensitive data. Use when proving a new integration path. Trigger with "Mistral hello world", "test my Mistral setup", or "make a first Mistral request". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: "<runtime> <environment> <model-alias>" version: 1.14.0 license: MIT author: Jeremy Longshore <[email protected]> tags: [saas, mistral, quickstart] model: inherit effort: high compatibility: "Designed for Claude Code; live or external Mistral actions require network access and explicit approval" --- # Mistral Bounded First Request ## Overview Prove the smallest useful chat path without turning a quickstart into production authority. Build offline, use synthetic text, capture content-free evidence, and stop after one approved response. ## Prerequisites - A configured server-side `MISTRAL_API_KEY` reference. - A current model identifier selected from account-visible evidence. - Approval for one billable request and a non-sensitive synthetic prompt. ## Current Contract The current chat surface is `POST /v1/chat/completions`. A request includes a model and messages; response and usage shapes come from the current endpoint schema. Model aliases and availability are mutable. ## Authentication Resolve the key only at runtime through the trusted client boundary. Do not print the key, headers, prompt, or response content in the receipt. ## Instructions 1. Inspect runtime and dependency lock before selecting the official client. 2. Resolve an allowed model dynamically; do not rely on an old price or context table. 3. Construct one deterministic message containing no secrets, personal data, or customer content. 4. Review parameters and maximum output before authorizing the live call. 5. Execute once after approval; record status, latency, returned model, finish reason, and usage. 6. Dispose of response content unless the approved plan explicitly retains the synthetic sample. ## 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 the live call, model, output bound, and retained response. Do not add retries, tools, files, or stateful resources. ## Error Handling - `401` is a configuration problem, not a reason to reveal a credential. - `429` requires current workspace evidence, not immediate repeated calls. - Model-not-found requires fresh discovery; never silently fall back to a costlier model. ## Output Return endpoint, requested/returned model, result class, latency, finish reason, usage, retention decision, and rollback. Redact content and credentials. ## Examples - Prove staging with the prompt `Reply with the word ready`. - Report `request_count=1; content_retained=no; usage_recorded=yes`. ## Validation Assert exactly one request, recognized shape, bounded output, usage capture, no sensitive data, no logging, and no fallback. ## 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-hello-world.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 Hello World 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 Hello World 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 Hello World access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Mistral Hello World 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.