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 streamthoughts/jikkou --skill managing-kafka-resourcesgit clone --depth 1 https://github.com/streamthoughts/jikkouWrote 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/streamthoughts/jikkou/managing-kafka-resources)<a href="https://agentmods.dev/skills/streamthoughts/jikkou/managing-kafka-resources"><img src="https://agentmods.dev/badge/skills/streamthoughts/jikkou/managing-kafka-resources.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
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 →
- medium MCP Rug Pull · line 44 Docker image references without a specific tag (:latest is implicit) or digest (@sha256:...) can be silently replaced by a malicious image.Fix: Pin the image: image:tag or image@sha256:abc123
- low Tool Misuse · line 44 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.00079 | $0.00992 |
| Opus 5 | $0.00039 | $0.00496 |
| Sonnet 5 | $0.00016 | $0.00198 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
managing-kafka-resources 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 8d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jikkou: Resource as Code for Apache Kafka
Declarative management of Kafka-ecosystem resources: YAML in, reconciliation against the real cluster out. Stateless: diff compares against live cluster state, never a state file.
Setup check (always run first)
jikkou --versionconfirms the CLI is on PATH. Missing? See "If jikkou is not installed".jikkou health get kafkaverifies connectivity (health get-indicatorsonly lists indicators; it doesn't check connectivity). For other providers usejikkou health get <indicator>; indicator names differ from provider names, seereferences/diagnostics.mdfor the exact list.- No context configured? Run
jikkou config current-contextandjikkou config view; config lives in~/.jikkou/config. See the context safety rule below.
Core workflow
Discover → author → validate → diff → apply. Never skip validate/diff.
- Inspect current state:
jikkou get <provider> <kind> -o JSON(providers: kafka, schemaregistry, kafkaconnect, aiven, confluent-cloud, aws, iceberg). Filter:--name <name>or-s 'metadata.name IN (a,b)'. - Discover kinds/schemas:
jikkou api-resources list, thenjikkou api-resources schema --api-version=<v> --kind=<k>.list → schema → write YAML → validate → diffis the canonical authoring chain. - Validate:
jikkou validate --files <file>returns normalized resources or errors. - Preview:
jikkou diff --files <file>shows the exact changes vs. the live cluster. - Apply:
jikkou apply --files <file> --dry-runfirst; drop--dry-runonly after the user confirms the diff.
Safety rules
- Never run
applywithout first showing the userdiffor--dry-runoutput. - Deleting a resource requires the annotation
jikkou.io/delete: trueon it — never delete another way. - Treat contexts named prod/production with extra confirmation before any non-dry-run apply.
- Never run
jikkou config use-contextcasually: jikkou eagerly loads the current context on every call, so a broken context bricks every command, not just the one you meant to try. Checkcurrent-context/config viewfirst; if a switch is truly needed, verify the target, then switch back.
What ships with it
9 files 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.
- 8d ago First seen · 55 lines · 79 tokens per session scan A 79e9eb9ff061
managing-kafka-resources is a skill published in the GitHub repository streamthoughts/jikkou (305 stars, last pushed 4d ago), licensed Apache-2.0. It adds 79 tokens to every session and 992 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
kafka-stream-processing
Complete guide for Apache Kafka stream processing including producers, consumers, Kafka Streams, connectors, schema registry, and production deployment.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
detecting-api-enumeration-attacks
Detect and prevent API enumeration attacks including BOLA and IDOR exploitation by monitoring sequential identifier access patterns and authorization failures.
exploiting-excessive-data-exposure-in-api
Tests APIs for excessive data exposure where endpoints return more data than the client application needs, relying on the frontend to filter sensitive fields. The tester intercepts API responses and analyzes them for leaked PII, internal identifiers, debug information, or sensitive business data that the UI does not…
implementing-api-rate-limiting-and-throttling
Implements API rate limiting and throttling controls using token bucket, sliding window, and fixed window algorithms to protect against brute force attacks, credential stuffing, resource exhaustion, and API abuse. The engineer configures per-user, per-IP, and per-endpoint rate limits using Redis-backed counters, API…