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.
git clone --depth 1 https://github.com/themoah/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/rules/themoah/klag/metrics)<a href="https://agentmods.dev/rules/themoah/klag/metrics"><img src="https://agentmods.dev/badge/rules/themoah/klag/metrics/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/rules/themoah/klag/metrics"><img src="https://agentmods.dev/badge/rules/themoah/klag/metrics.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.00000 | $0.00412 |
| Opus 5.5 | $0.00000 | $0.00165 |
| Sonnet 5.5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
metrics 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.
What it actually says
Metrics
Public API — names and tags are stable contracts.
Core metrics
klag.consumer.lag[.sum/.max/.min]— per partition; aggregates perconsumer_group+topicklag.consumer.lag.velocity— msg/sec × 100klag.consumer.lag.ms— time lag; per-partition + topic rollup ({partition=""}/{partition!=""})klag.consumer.lag.time_to_close_seconds—consumer_group+topiconlyklag.consumer.lag.retention_percent— DLP; same partition rollup pattern aslag.msklag.consumer.commit.staleness_seconds— inferred commit freshness; only while lag > 0klag.consumer.group.state— state as tag; two-phase stale-gauge cleanup on transitionsklag.partition.under_replicated,klag.hot_partition[.lag]— partition-level; conditional emissionklag.topic.size_skew— topic-level max/mean retained-size ratio × 100; opt-in viaDATA_SKEW_ENABLED(default false)
Member labels (member_host, consumer_id, client_id) on per-partition consumer metrics when CONSUMER_MEMBER_LABELS_ENABLED=true (default).
When adding or changing a metric
Update all of:
- Collector/reporter code + tests
CLAUDE.mdandREADME.mdmetric sectionsdashboard/demo-dashboard.json(and Grafana.com export if applicable)- Helm chart/README if scrape or ServiceMonitor behavior changes
- Website docs under
website/src/content/docs/metrics/when user-facing
Never ship a new metric without a dashboard panel.
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 Changed · +1 lines dca2a1fabb73
- 1mo ago First seen · 37 lines · 0 tokens per session scan A 9d59d5b8e060
metrics is a cursor rule published in the GitHub repository themoah/klag (88 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 412 tokens. 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 cursor rules, from other repositories
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
rule-calling-help
Utility for remembering how to call VAN QA rules.
bsl-method-description
A set of rules for writing comments that describe methods in Russian-language code. It covers placement, parameters, links to related methods, compiler directives, and examples for exported methods.
common-fixes
Utility for VAN QA common validation fixes.