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 skills add lensesio/agentic-engineering-for-apache-kafka --skill kafka-connector-reviewgit clone --depth 1 https://github.com/lensesio/agentic-engineering-for-apache-kafkaWrote 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/lensesio/agentic-engineering-for-apache-kafka/kafka-connector-review)<a href="https://agentmods.dev/skills/lensesio/agentic-engineering-for-apache-kafka/kafka-connector-review"><img src="https://agentmods.dev/badge/skills/lensesio/agentic-engineering-for-apache-kafka/kafka-connector-review/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/lensesio/agentic-engineering-for-apache-kafka/kafka-connector-review"><img src="https://agentmods.dev/badge/skills/lensesio/agentic-engineering-for-apache-kafka/kafka-connector-review.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.00079 | $0.01727 |
| Opus 5 | $0.00039 | $0.00864 |
| Sonnet 5 | $0.00016 | $0.00345 |
| Haiku 4.5 | $0.00008 | $0.00173 |
Grade A, and why
kafka-connector-review 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 12d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kafka Connect Configuration Review
Reviews Kafka Connect connector configurations for common misconfigurations. Connectors are defined as JSON/YAML and are entirely language-agnostic.
Target environment: $ARGUMENTS
Workflow
Copy this checklist and track your progress:
Connector Review Progress:
- [ ] Step 1: List all connectors
- [ ] Step 2: Inspect each connector's configuration
- [ ] Step 3: Validate configurations against plugin schemas
- [ ] Step 4: Audit for common misconfigurations
- [ ] Step 5: Generate report
- List all connectors with status and task states
- Inspect each connector's configuration in detail
- Validate configurations against plugin schemas
- Audit for common misconfigurations
- Report findings with current and recommended configs
Step 1: List All Connectors
Use the Lenses MCP list_kafka_connectors tool to get all connectors with:
- Connector name, class and type (source/sink)
- Status (RUNNING, PAUSED, FAILED, UNASSIGNED)
- Task states and count
- Cluster info
Flag immediately:
- Critical: Connectors in FAILED state
- Critical: Tasks in FAILED state
- Warning: Connectors in PAUSED state with no obvious reason
Expected output: List of all connectors with name, class, status and task states.
Validation: If no connectors are returned, report that no Connect cluster is configured and stop.
Step 2: Inspect Configurations
Use the Lenses MCP get_kafka_connector_target_definition tool to get the full configuration YAML for each connector.
Step 3: Validate Configurations
Use the Lenses MCP validate_connector_configuration tool to validate each connector's config against its plugin's schema. This catches:
- Missing required configuration fields
- Invalid configuration values
- Type mismatches
Step 4: Audit Common Misconfigurations
Error Handling
- Critical:
errors.tolerance=allwithouterrors.deadletterqueue.topic.name(silently drops messages) - Warning: Missing
errors.tolerance(defaults tonone, connector stops on any error) - Warning: Missing
errors.log.enable=true(errors not logged) - Suggestion: Add
errors.deadletterqueue.context.headers.enable=truefor richer DLQ metadata
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 195 lines · 79 tokens per session scan A d4991cb04492
kafka-connector-review is a skill published in the GitHub repository lensesio/agentic-engineering-for-apache-kafka (57 stars, last pushed 21d ago), licensed MIT. It adds 79 tokens to every session and 1,727 once invoked, about $0.0004 per session on Opus 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
sdd-apply
Skill "sdd-apply" from Gentleman-Programming/gentle-ai, covering execution role, language domain contract, purpose, what you receive and execution and persistence contract.
fec-data-fetching
A frontend guide for handling data that comes from a server, including typed requests, caching, refreshing, pagination, and updates. Server state means data owned by an API rather than by a page’s local controls.
agent-java-reviewer
Expert Java code reviewer for Spring Boot and Quarkus projects. Automatically detects the framework and applies the appropriate review rules. Covers layered architecture, JPA/Panache, MongoDB, security, and concurrency. MUST BE USED for all Java code changes.
agent-django-reviewer
Expert Django code reviewer specializing in ORM correctness, DRF patterns, migration safety, security misconfigurations, and production-grade Django practices. Use for all Django code changes. MUST BE USED for Django projects.
fec-react-project-standard
A guide for organizing medium-sized or large React and TypeScript projects. It defines boundaries between pages, business features, shared components, hooks, services, state, APIs, and utilities.
agent-fastapi-reviewer
Reviews FastAPI applications for async correctness, dependency injection, Pydantic schemas, security, OpenAPI quality, testing, and production readiness.