Agent skill · security · jeremylongshore
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".
Why this skill is useful
Provides specific security practices and code snippets for managing API keys and defending against prompt injection in Mistral AI integrations.
What it needs
Requires mistral account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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. Authentication Keep keys server-side and environment-scoped; rotate on exposure. Enforce user and tenant authorization before retrieval, provider calls, files, and tools. Instructions 1. Map trust boundaries and classify prompts, outputs, embeddings, files, logs, and IDs. 2. Remove credentials and privileged instructions from browser/untrusted contexts. 3. Separate trusted policy from untrusted content and delimit retrieved text as data. 4. Validate output structure and safety before render, storage, or tool use. 5. Authorize tools via closed registry, schemas, least privilege, deadlines, and idempotency. 6. Test injection, cross-tenant access, unsafe output, exfiltration, duplicates, and rotation. 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 sensitive data, uploads, stateful APIs, tools, policy changes, retention, or live attack testing. Model output never grants authority. Error Handling Prompt wording cannot enforce access control. Moderation success does not prove correctness or tool safety. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/mistral-security-basics