Individual skill

mistral-security-basics

Threat-model Mistral credentials, untrusted content, model output, tools, files, and tenant access. Use when securing or reviewing an integration. Trigger with "secure Mistral", "audit Mistral prompts", or "threat model a Mistral app".

skills/.curated/mistral-security-basics/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,916
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# Mistral Security Boundary

## Overview

Apply controls at the application boundary because model instructions do not enforce identity, tenancy, authorization, or side-effect safety. Treat user content, retrieval, files, and output as untrusted.

## Prerequisites

- A data-flow diagram covering browser, app, Mistral, stores, and tools.
- Credential, retention, tenant, moderation, and incident policies.
- An inventory of stateful APIs, files, retrieval stores, and actions.

## Current Contract

Bearer credentials authorize provider calls but not application users. Classifiers can support policy but do not replace controls. ZDR eligibility differs between stateless and stateful products.
Back to top