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.
/plugin marketplace add themoah/klagnpx agentmods add plugins/themoah/klag/marketplacegit clone --depth 1 https://github.com/themoah/klagGrade A, and why
klag 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 2d 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.
What it actually says
{
"$schema": "https://code.claude.com/schemas/marketplace.json",
"name": "klag",
"description": "The Klag Kafka consumer lag exporter: install it, connect its MCP endpoint, and triage consumer lag from your agent.",
"owner": {
"name": "themoah",
"url": "https://klag.dev"
},
"plugins": [
{
"name": "klag",
"source": "./plugin",
"description": "Install, connect and diagnose Klag — the Kafka consumer lag exporter."
}
]
}
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.
- 2d ago First seen · 17 lines scan A 216adeef5220
klag is a plugin published in the GitHub repository themoah/klag (81 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
jikkou
Official Jikkou skills for AI agents: manage Kafka topics, ACLs, quotas, schemas, and connectors declaratively with the Jikkou CLI.
jikkou
Plugin marketplace listing 1 plugin: jikkou.
chmonitor
Specialized assistance for the chmonitor dashboard - a real-time monitoring dashboard for ClickHouse clusters.
monitoring-aiops
Governed SolarWinds Orion + PRTG + Zabbix ops: SWQL, alert rollup, health, 42 tools.
claude-code-monitor
Local usage, cost and failure dashboard for Claude Code. Auto-starts on session start; open http://localhost:8787.
zapi-mcp
Zabbix API for Claude Code, via an API user. Investigate active problems, hosts, and item values, get a one-shot dailybrief health check, acknowledge problems, and open maintenance windows. Site-specific dailybrief categories (DHCP pool usage, SNAT usage, core-network, …) need a local ZABBIXCATEGORIESINI file that.