A delegation skill that sends straightforward coding work to the Mistral Vibe command-line tool, an external coding agent powered by Devstral 2.1.

Use it for simple refactors, boilerplate, test scaffolding, documentation updates, and similar clearly specified file changes.

It can handle well-defined, mechanical work while leaving more complex reasoning to the main agent, provided Vibe is installed and configured.

vibe — Skill for Claude Code by kharonsec/vibe-plugin

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add kharonsec/vibe-plugin --skill vibe

Clone the repo

git clone --depth 1 https://github.com/kharonsec/vibe-plugin

Made for: Claude Code.

Or install skill-vibe, the plugin that ships this one along with the rest of its 1 skill.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kharonsec/vibe-plugin/vibe/github.svg)](https://agentmods.dev/skills/kharonsec/vibe-plugin/vibe)

Your own site

<a href="https://agentmods.dev/skills/kharonsec/vibe-plugin/vibe"><img src="https://agentmods.dev/badge/skills/kharonsec/vibe-plugin/vibe/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kharonsec/vibe-plugin/vibe"><img src="https://agentmods.dev/badge/skills/kharonsec/vibe-plugin/vibe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,811 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00133	$0.01811
Opus 5.5	$0.00053	$0.00724
Sonnet 5.5	$0.00027	$0.00362
Haiku 4.5	$0.00013	$0.00181

Measured 1mo ago against content hash fa5d45ac7550, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

vibe scanned grade C with 2 findings 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 1mo 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- `vibe` CLI installed and on `PATH` (install: `curl -LsSf https://mistral.ai/vibe/install.sh | bash`)

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `vibe` CLI installed and on `PATH` (install: `curl -LsSf https://mistral.ai/vibe/install.sh | bash`)

plugins/skill-vibe/skills/vibe/SKILL.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mistral Vibe CLI Delegation Skill

Delegate simple, well-defined coding tasks to Mistral's Vibe CLI agent (powered by Devstral 2.1) to save Claude tokens for harder problems. Vibe runs non-interactively via --prompt and returns results that Claude summarizes for the user.

Prerequisites

vibe CLI installed and on PATH (install: curl -LsSf https://mistral.ai/vibe/install.sh | bash)
Mistral API key configured (~/.vibe/.env or MISTRAL_API_KEY env var)
Confirm installation: vibe --version; resolve any errors before using this skill

If vibe is not installed or not configured, inform the user and provide the installation instructions above. Do NOT attempt to run vibe commands if the prerequisites are not met.

How It Works

Claude evaluates the user's request
If the task is simple/mechanical, Claude delegates to Vibe via a shell command
Vibe runs non-interactively with --prompt, auto-approving tool executions
Claude reads the output and summarizes results back to the user
If Vibe's output is insufficient or incorrect, Claude can either retry with a refined prompt or fall back to handling the task itself

Task Routing Guidelines

Delegate to Vibe (cheap, fast)

Boilerplate generation (new files, structs, interfaces, CRUD endpoints)
Simple refactors (rename, extract function, move code between files)
Test scaffolding and simple test writing
Documentation and comment generation
Formatting, linting fixes, import sorting
Dependency version bumps
Mechanical find-and-replace across files
Adding error handling to straightforward functions
Generating type definitions or interfaces from existing code
Simple bug fixes where the issue is clearly identified

Keep in Claude (complex, nuanced)

Architectural decisions or design pattern selection
Security-sensitive code review or vulnerability analysis
Complex multi-step debugging requiring deep reasoning
Performance optimization requiring profiling analysis
Tasks requiring understanding of the full project context across many files
Anything the user explicitly wants Claude to handle

Read the full file on GitHub · 177 lines

Changes

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.

1mo ago First seen · 177 lines · 133 tokens per session scan C fa5d45ac7550

Subscribe to this mod's changes

vibe is a skill published in the GitHub repository kharonsec/vibe-plugin (4 stars, last pushed 7mo ago), licensed MIT. It adds 133 tokens to every session and 1,811 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

vibe