Mistral Vibe is a command-line coding assistant that lets users converse with a codebase and use natural language to explore or change projects. Developers use it for file editing, code searching, version-control tasks, and shell commands through Mistral’s models. Its catalogue add-ons provide skills and instructions for customizing the assistant’s workflows.
Borrowing it
Nothing to install: this file belongs to mistralai/mistral-vibe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mistralai/mistral-vibe/main/.agents/skills/vibe-ci-supply-chain/SKILL.mdgit clone --depth 1 https://github.com/mistralai/mistral-vibeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mistralai/mistral-vibe/vibe-ci-supply-chain)<a href="https://agentmods.dev/skills/mistralai/mistral-vibe/vibe-ci-supply-chain"><img src="https://agentmods.dev/badge/skills/mistralai/mistral-vibe/vibe-ci-supply-chain/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mistralai/mistral-vibe/vibe-ci-supply-chain"><img src="https://agentmods.dev/badge/skills/mistralai/mistral-vibe/vibe-ci-supply-chain.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 23 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.01027 |
| Opus 5 | $0.00030 | $0.00513 |
| Sonnet 5 | $0.00012 | $0.00205 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
vibe-ci-supply-chain scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Container images**: reference by `@sha256:<digest>`, never a bare tag (`:latest`, `:8`). Resolve the digest via the registry's `Docker-Content-Digest` header (`curl -sI -H 'Accept: application/vnd.oci.image.index.v1+ How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe CI & Supply Chain
Conventions for git workflow, CI configuration, and supply-chain security in Vibe.
Startup import cost
CI gates cold-start module count via vibe/scripts/check_startup_import_cost.py (budgets in vibe/scripts/startup_import_cost.vibe.toml).
- When a change touches imports or module structure on the path of
import vibeorfrom vibe.cli.textual_ui.app import VibeApp, runcd vibe && uv run scripts/check_startup_import_cost.pyand confirm the count stays within budget. - Verify, do not bump. An overshoot is a regression to investigate (lazy import, drop the dependency, defer the import) — not a reason to raise the budget. Only widen for a deliberate, PR-justified increase, and set to observed count + ~10% headroom, never the exact count.
Git
- Never use
git commit --amend,git push --force, orgit push --force-with-lease. - Always create new commits and push with a plain
git push. - Reconciling with the upstream of the current branch (e.g. push rejected because
origin/<current-branch>advanced): rebase the current branch onto its upstream — do not merge the upstream branch into the current one, never force-push. - Reconciling with the base branch (e.g.
origin/main) once the PR is open: merge the base branch into the current branch — do not rebase, since rebasing rewrites already-pushed history and would require a force-push. - Run git commands through
uv run(e.g.uv run git commit,uv run git push) so pre-commit hooks resolve the project's venv — baregit commitfails pre-commit withreportMissingImportsbecause pyright can't find third-party packages.
CI / GitHub Actions
- Pin every
uses:to a full commit SHA with an exact version comment:uses: owner/action@<commit-sha> # vX.Y.Z. - Resolve to the commit, not the annotated-tag object: take the
refs/tags/vX^{}line fromgit ls-remote --tags, orgh api repos/<owner>/<repo>/git/refs/tags/<tag> --jq .objectpeeled to a commit. Check withgit cat-file -t <sha>→commit, nottag. Never pin a moving major tag (v9).
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 42 lines · 59 tokens per session scan A 601db05018b1
vibe-ci-supply-chain is a skill published in the GitHub repository mistralai/mistral-vibe (4,935 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 1,027 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.