alert-analyzer

alert-analyzer is an agent for Claude Code from lhfer/claude-howto-zh-cn. It costs 12 tokens per session (71 once invoked), scanned A, original, MIT.

An agent for analysing monitoring alerts and system metrics. The description is in Chinese and says it handles alert correlation, trend analysis, root-cause investigation, metric interpretation, and proactive risk discovery.

In plain words
What is it for?
Reviewing monitoring alerts, finding related events, identifying likely causes, interpreting metrics and trends, and spotting possible risks early.
Why use it?
It helps organise information from alerts and metrics so related incidents, trends, and possible causes can be examined together. The input does not specify particular systems or data sources.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the devops-automation plugin — 4 commands, 3 agents shipped together

Good fit Reviewing monitoring alerts, finding related events, identifying likely causes, interpreting metrics and trends, and spotting possible risks early.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/lhfer/claude-howto-zh-cn/alert-analyzer
About the project

Claude Code 中文全面上手指南 is a Chinese-language learning guide for using Claude Code and combining features such as commands, memory, skills, hooks, MCP, subagents, and plugins. It is aimed at Chinese beginners and provides learning paths, examples, and compatibility guidance, while the catalogue entries package parts of that guidance as agent resources.

lhfer/claude-howto-zh-cn · 2,293 stars · on GitHub

Install

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.

Clone the repo
git clone --depth 1 https://github.com/lhfer/claude-howto-zh-cn

Made for: Claude Code.

Or install devops-automation, the plugin that ships this one along with the rest of its 4 commands, 3 agents.

Wrote 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.

agentmods badge for alert-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/lhfer/claude-howto-zh-cn/alert-analyzer/github.svg)](https://agentmods.dev/agents/lhfer/claude-howto-zh-cn/alert-analyzer)
Your own site
<a href="https://agentmods.dev/agents/lhfer/claude-howto-zh-cn/alert-analyzer"><img src="https://agentmods.dev/badge/agents/lhfer/claude-howto-zh-cn/alert-analyzer/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.

agentmods 80×15 button for alert-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/agents/lhfer/claude-howto-zh-cn/alert-analyzer"><img src="https://agentmods.dev/badge/agents/lhfer/claude-howto-zh-cn/alert-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 71 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.00071
Opus 5 $0.00006 $0.00036
Sonnet 5 $0.00002 $0.00014
Haiku 4.5 $0.00001 $0.00007

Measured 11d ago against content hash 530c9be57951, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

alert-analyzer 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 11d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

07-plugins/devops-automation/agents/alert-analyzer.md · 16 lines

What it actually says

Alert Analyzer / 告警分析代理

负责:

  • 告警关联分析
  • 趋势判断
  • 根因定位
  • 指标解读
  • 主动发现风险
Changes

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.

  1. 11d ago First seen · 16 lines · 12 tokens per session scan A 530c9be57951

Subscribe to this mod's changes

alert-analyzer is an agent published in the GitHub repository lhfer/claude-howto-zh-cn (2,293 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 71 once invoked, about $0.0001 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.