Confluent MCP Server is an open-source Model Context Protocol server that lets AI assistants interact with Confluent Cloud, Confluent Platform, and standalone Apache Kafka through natural language. Its tools cover Kafka, Flink SQL, Schema Registry, connectors, and Tableflow. The catalogue add-ons help agents operate and configure the server.
Borrowing it
Nothing to install: this file belongs to confluentinc/mcp-confluent. 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/confluentinc/mcp-confluent/main/.claude/skills/vitest/SKILL.mdgit clone --depth 1 https://github.com/confluentinc/mcp-confluentWrote 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/confluentinc/mcp-confluent/vitest)<a href="https://agentmods.dev/skills/confluentinc/mcp-confluent/vitest"><img src="https://agentmods.dev/badge/skills/confluentinc/mcp-confluent/vitest/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/confluentinc/mcp-confluent/vitest"><img src="https://agentmods.dev/badge/skills/confluentinc/mcp-confluent/vitest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.01567 |
| Opus 5.5 | $0.00035 | $0.00627 |
| Sonnet 5.5 | $0.00017 | $0.00313 |
| Haiku 4.5 | $0.00009 | $0.00157 |
Grade A, and why
vitest scanned grade A with 0 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vitest Documentation Lookup
Look up Vitest APIs, patterns, and best practices via WebFetch against the official docs. Use this
skill to answer questions about vi.*, mock instances, assertions, fake timers, and config
options. Project-specific test conventions (naming, stubbing strategy, node-deps.ts pattern) live
in .claude/rules/unit-tests.md - reference that rule rather than re-deriving the conventions.
Sources
Base URL: https://vitest.dev
| Topic | Path | Use for |
|---|---|---|
| Getting started | /guide/ |
General concepts, project setup, runner behavior |
| Mocking guide | /guide/mocking |
Worked examples: modules, timers, dates, classes |
| Config reference | /config/ |
vitest.config.ts options (restoreMocks, pool, coverage) |
vi API |
/api/vi |
Top-level helpers (vi.fn, vi.spyOn, vi.mocked, timers) |
| Mock instance API | /api/mock |
Methods on a Mock (.mockReturnValue, .mockImplementation) |
| Assertions | /api/expect |
expect() matchers, argument matchers |
| Fake timers | /api/vi#vi-usefaketimers |
vi.useFakeTimers, advanceTimersByTimeAsync |
| CLI | /guide/cli |
vitest run, flags, watch mode |
Process
-
Determine the question type
- API reference (exact signature, options, return type) →
/api/*pages - Pattern guidance / worked examples →
/guide/mockingor/guide/ - Config option behavior →
/config/ - CLI flag / runner behavior →
/guide/cli
- API reference (exact signature, options, return type) →
-
Check project rules first - read
.claude/rules/unit-tests.mdbefore fetching. It already documents:restoreMocks: truebehavior, thenode-deps.tsnamespace pattern,createMockInstance, constructor-stub gotchas, and thevi.mockanti-pattern. Don't re-explain these; cite the rule and only fetch docs for anything beyond it.
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 · 144 lines · 87 tokens per session scan A 5f82171404fc
vitest is a skill published in the GitHub repository confluentinc/mcp-confluent (168 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 1,567 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.