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.
npx agentmods add skills/kharonsec/vibe-plugin/vibenpx skills add kharonsec/vibe-plugin --skill vibegit clone --depth 1 https://github.com/kharonsec/vibe-pluginWrote 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/kharonsec/vibe-plugin/vibe)<a href="https://agentmods.dev/skills/kharonsec/vibe-plugin/vibe"><img src="https://agentmods.dev/badge/skills/kharonsec/vibe-plugin/vibe.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00133 | $0.01811 |
| Opus 5 | $0.00067 | $0.00905 |
| Sonnet 5 | $0.00027 | $0.00362 |
| Haiku 4.5 | $0.00013 | $0.00181 |
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 3d 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`) 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
vibeCLI installed and onPATH(install:curl -LsSf https://mistral.ai/vibe/install.sh | bash)- Mistral API key configured (
~/.vibe/.envorMISTRAL_API_KEYenv 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
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.
- 3d ago First seen · 177 lines · 133 tokens per session scan C fa5d45ac7550
vibe is a skill published in the GitHub repository kharonsec/vibe-plugin (4 stars, last pushed 5mo ago), licensed MIT. It adds 133 tokens to every session and 1,811 once invoked, about $0.0007 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
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…