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.
npx agentmods add commands/with-geun/alive-analysis/monitor-checkgit clone --depth 1 https://github.com/with-geun/alive-analysisWrote 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/with-geun/alive-analysis/monitor-check)<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>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 | $0.00000 | $0.01534 |
| Opus 5 | $0.00000 | $0.00767 |
| Sonnet 5 | $0.00000 | $0.00307 |
| Haiku 4.5 | $0.00000 | $0.00153 |
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.
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
--allflag: 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:
- Read the monitor file from
.analysis/metrics/monitors/{ID}_{slug}.md - Read the linked metric definition from
.analysis/metrics/definitions/ - 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 |
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.
- 5d ago First seen · 177 lines · 0 tokens per session scan A 22eed360070a
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.
Other commands, from other repositories
help
아래 레퍼런스 카드를 사용자에게 그대로 보여주고, 상황에 맞는 다음 한 걸음을 한 줄로 추천하세요 (.oculpm/ 이 없으면 /oculpm:projectinit, 활성 플랜이 있으면 /oculpm:next).
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
next
활성 플랜의 다음 미완 리프를 잡아 구현 — 구현→검증→일지→플랜 갱신 한 사이클.
standup
ocul-pm 추적 프로젝트의 오늘 작업 스탠드업 — 일지·플랜 진행을 모아 요약 보고.
inception
새 프로젝트/기능 영역의 설계 시작 — 리서치→사양 확정→3-depth 계획→EVALS→rules 시드.
generate-extension
Create Shopify app extension (Functions, Theme App Extension, or Admin UI) with proper scaffolding and configuration.