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-listgit 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-list)<a href="https://agentmods.dev/commands/with-geun/alive-analysis/monitor-list"><img src="https://agentmods.dev/badge/commands/with-geun/alive-analysis/monitor-list.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.00758 |
| Opus 5 | $0.00000 | $0.00379 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
monitor-list 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/monitor list
Show all metric monitors with their current status.
Instructions
Step 1: Scan monitors
Read all files in .analysis/metrics/monitors/ matching M-*.md.
For each monitor, extract from the header:
- ID
- Metric name
- Status (🟢/🟡/🔴)
- Last checked date
- Check cadence
Step 2: Scan recent alerts
Read .analysis/metrics/alerts/ for the current and previous month.
For each alert, extract:
- Alert ID
- Monitor ID (to link back)
- Severity (🟡/🔴)
- Date
- Resolved status
Step 3: Display dashboard
═══════════════════════════════════════════════════
Metric Monitors — {date}
═══════════════════════════════════════════════════
Summary
───────
🟢 Healthy: {count}
🟡 Warning: {count}
🔴 Critical: {count}
⚪ Not yet checked: {count}
All Monitors ({total})
──────────────────────
| ID | Metric | Cadence | Status | Last Checked | Alerts (30d) |
|----|--------|---------|--------|-------------|--------------|
| M-2026-0301-001 | DAU | daily | 🟢 | 2026-03-05 | 0 |
| M-2026-0301-002 | Conversion Rate | weekly | 🟡 | 2026-03-03 | 1 |
| M-2026-0302-001 | Error Rate | daily | 🔴 | 2026-03-05 | 2 |
Recent Alerts ({count})
───────────────────────
| Alert ID | Monitor | Metric | Severity | Date | Resolved? |
|----------|---------|--------|----------|------|-----------|
| A-2026-0305-001 | M-...-002 | Conversion Rate | 🟡 | 2026-03-05 | No |
| A-2026-0304-001 | M-...-001 | Error Rate | 🔴 | 2026-03-04 | Yes → F-2026-0304-001 |
═══════════════════════════════════════════════════
Step 4: Highlight overdue checks
For each monitor, compare the last checked date against the cadence:
- Daily: overdue if last checked > 1 day ago
- Weekly: overdue if last checked > 7 days ago
- Monthly: overdue if last checked > 30 days ago
If overdue, show: ⏰ {metric} is overdue for a check (last: {date}, cadence: {cadence})
Step 5: Optional filters
If the user provides arguments:
/monitor list --status warning→ show only 🟡 monitors/monitor list --status critical→ show only 🔴 monitors/monitor list --overdue→ show only overdue monitors/monitor list --alerts→ show only monitors with unresolved alerts
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 · 85 lines · 0 tokens per session scan A 2f9f28b08ea8
monitor-list 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 758 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
next
활성 플랜의 다음 미완 리프를 잡아 구현 — 구현→검증→일지→플랜 갱신 한 사이클.
project_init
이 프로젝트를 ocul-pm 추적 대상으로 초기화 (.oculpm/ + 기록 규칙 생성) — 사용자가 직접 실행하는 명시적 시작.
standup
ocul-pm 추적 프로젝트의 오늘 작업 스탠드업 — 일지·플랜 진행을 모아 요약 보고.
inception
새 프로젝트/기능 영역의 설계 시작 — 리서치→사양 확정→3-depth 계획→EVALS→rules 시드.
optimize-listing
Optimize Shopify App Store listing for search discovery, conversion, and Built for Shopify certification requirements.
audit-scopes
Audit and minimize API scopes for security, verify scope usage, and generate scope justification for App Store submission.