monitor-check

monitor-check is a command for Claude Code from with-geun/alive-analysis. It costs 0 tokens per session (1,534 once invoked), scanned A, original, MIT.

A command that checks one or all configured metric monitors against their thresholds. Thresholds are limits used to decide when a metric needs attention.

In plain words
What is it for?
Use it with a monitor ID or `--all`, then provide current data manually, from a file, or through a configured data query; it records the result and creates alerts when needed.
Why use it?
It turns a current metric value into a recorded health result and can reveal warnings, critical changes, or segment-specific problems.

Command for Claude Code

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.

agentmods
npx agentmods add commands/with-geun/alive-analysis/monitor-check
Clone the repo
git clone --depth 1 https://github.com/with-geun/alive-analysis

Made for: Claude Code.

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 monitor-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/with-geun/alive-analysis/monitor-check.svg)](https://agentmods.dev/commands/with-geun/alive-analysis/monitor-check)
Your own site
<a href="https://agentmods.dev/commands/with-geun/alive-analysis/monitor-check"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/monitor-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,534 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.01534
Opus 5 $0.00000 $0.00767
Sonnet 5 $0.00000 $0.00307
Haiku 4.5 $0.00000 $0.00153

Measured 5d ago against content hash 22eed360070a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

monitor-check 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 5d 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.

.claude/commands/monitor-check.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/monitor check

Run a metric health check on one or all monitors.

Instructions

Step 1: Determine scope

  • If argument provided (monitor ID): check that specific monitor
  • If --all flag: check all active monitors
  • If no argument: show list and ask user which to check, or offer "check all"

Step 2: Read monitor configuration

For each monitor to check:

  1. Read the monitor file from .analysis/metrics/monitors/{ID}_{slug}.md
  2. Read the linked metric definition from .analysis/metrics/definitions/
  3. Note: check cadence, comparison basis, thresholds, auto-segment setting

Step 3: Gather data

Ask the user for the current metric value(s).

Three data collection paths:

  • MCP query: If MCP is configured in config.md, suggest running a query
  • Manual input: "What's the current value of {metric}?"
  • File/screenshot: "Paste or upload the latest data"

If auto-segment is enabled:

  • Also ask for segment-level values (or suggest MCP query to get breakdown)

Step 4: Evaluate

Compare the current value against the monitor's configuration.

First check (no history)? If the Check History table is empty (this is the first check):

  • Record the current value as the baseline — skip comparison-based evaluation
  • Evaluate against absolute thresholds only (healthy range from the metric definition), if defined
  • If no absolute thresholds available, mark status as 📊 Baseline recorded
  • Tell the user: "This is the first check. Recording {value} as your baseline. Meaningful comparisons will begin on the next check."
  • Proceed directly to Step 7 (Update monitor file) — no alerts on the first check

Normal check (history exists):

Comparison calculation:

Basis Formula
WoW (current - last_week) / last_week × 100
MoM (current - last_month) / last_month × 100
YoY (current - same_period_last_year) / same_period_last_year × 100
Rolling avg current vs {N}-day rolling average
Fixed target current vs target

Read the full file on GitHub · 177 lines

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. 5d ago First seen · 177 lines · 0 tokens per session scan A 22eed360070a

Subscribe to this mod's changes

monitor-check is a command published in the GitHub repository with-geun/alive-analysis (41 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,534 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.