Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add themoah/klag/plugin install klagWrote 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/commands/themoah/klag/install)<a href="https://agentmods.dev/commands/themoah/klag/install"><img src="https://agentmods.dev/badge/commands/themoah/klag/install/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/commands/themoah/klag/install"><img src="https://agentmods.dev/badge/commands/themoah/klag/install.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00026 | $0.01162 |
| Opus 5.5 | $0.00010 | $0.00465 |
| Sonnet 5.5 | $0.00005 | $0.00232 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
install scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "$KLAG_URL/readyz" How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up Klag for the user. Target hint: $ARGUMENTS (may be empty — then detect).
Read ${CLAUDE_PLUGIN_ROOT}/skills/klag/SKILL.md and
${CLAUDE_PLUGIN_ROOT}/skills/klag/references/deploy-targets.md first. Read
references/kafka-connect.md once you know the Kafka is not a local plaintext one.
Confirm before every command that mutates the user's machine or cluster, showing the exact command. Detection is read-only and needs no confirmation.
1. Detect
Run the detection block from deploy-targets.md (docker, kube context, helm, ArgoCD/Flux CRDs,
Strimzi CRDs, Prometheus Operator CRDs, java). Report what you found in two or three lines.
If the kube context matches prod|production|prd, say so explicitly and get a separate
confirmation before touching it.
2. Choose the target
Use AskUserQuestion, ordering options by what you detected. If $ARGUMENTS names a target, skip
this step. Options:
- Demo POC — the repo's
docker-compose.yaml: Kafka + Klag + a producer + three misbehaving consumers, so real lag appears in about a minute. Best when the user has no Kafka handy or just wants to see it work. Needs a checkout ofthemoah/klag. - Docker — one container against their Kafka.
- Kubernetes (Helm) — chart from
https://themoah.github.io/klag. - GitOps — ArgoCD
Application/ FluxHelmReleasewritten to their config repo, not applied. - Jar / native image — no docker. The published native build is the
themoah/klag:nativeimage; a standalone binary needs a source build with GraalVM JDK 21.
3. Kafka connection
Skip for the Demo POC. Otherwise discover the bootstrap servers rather than asking when you can
(Strimzi CR, kubectl get svc -A | grep -i kafka, an existing consumer Deployment's env). Confirm
the value with the user either way, then work out the auth from references/kafka-connect.md.
Secrets rule: credentials go into a Kubernetes Secret referenced by kafka.existingSecret. That
is the normal path. --set kafka.saslJaasConfig=... is a throwaway-POC shortcut only — it leaves
the value in the Helm release and in shell history — so name that trade-off when you use it. Never
write credentials into a values.yaml that sits in a git worktree, and never echo them back.
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 · 91 lines · 26 tokens per session scan A bb7847d0ae35
install is a command published in the GitHub repository themoah/klag (88 stars, last pushed 5d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,162 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
migration-observability
Migration monitoring, CDC, and observability infrastructure.
migration-observability
Migration monitoring, CDC, and observability infrastructure.
migration-observability
Migration monitoring, CDC, and observability infrastructure.
migration-observability
Migration monitoring, CDC, and observability infrastructure.
migration-observability
Migration monitoring, CDC, and observability infrastructure.
migration-observability
Migration monitoring, CDC, and observability infrastructure.