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/hoangsonww/Claude-Code-Agent-MonitorWrote 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/hoangsonww/claude-code-agent-monitor/anomalies)<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/anomalies"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/anomalies/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/commands/hoangsonww/claude-code-agent-monitor/anomalies"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/anomalies.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.00011 | $0.00423 |
| Opus 5 | $0.00005 | $0.00211 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
anomalies scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -s "http://localhost:4820/api/sessions?limit=200"` → a session list; each item has `id`, `status`, `model`, `cwd`, `started_at`, `cost`, and `metadata`. What it actually says
List the current cost/token outlier sessions from the Agent Monitor dashboard using a z-score test. $ARGUMENTS optionally sets the z-score threshold (default 2.0; lower = stricter).
-
Fetch the population:
curl -s "http://localhost:4820/api/sessions?limit=200"→ a session list; each item hasid,status,model,cwd,started_at,cost, andmetadata.
-
Compute the baseline over all returned sessions:
- Mean and standard deviation of
cost. - For sessions where you need token totals, pull
curl -s http://localhost:4820/api/pricing/cost/<id>and suminput_tokens + output_tokens + cache_read_tokens + cache_write_tokens; compute mean and stddev of total tokens too.
- Mean and standard deviation of
-
Flag outliers: any session whose
z = (value − mean) / stddevexceeds the threshold (default 2.0) on cost (primary) or tokens (secondary). Skip the calc gracefully if stddev is 0. -
Print the flagged sessions, sorted by descending cost z-score:
- Session id (short), model, started_at.
- Cost (USD, 4 decimals) and its z-score.
- Total tokens and its z-score (when fetched).
- A flag tag: 🔴 if z > 3, 🟡 if z > 2.
Output rules: a Markdown table of flagged sessions only; currency in USD to 4 decimals; z-scores to 2 decimals; if nothing exceeds the threshold, say "No cost/token outliers above z=" and report the top session by cost for context. Cite only API values — never fabricate. If the dashboard is unreachable at http://localhost:4820, tell the user to start it with npm start from the repo root.
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.
- 8d ago First seen · 24 lines · 11 tokens per session scan A 6a9244965be0
anomalies is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 423 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
commit
Smart conventional commit with security validation, branch flow enforcement, and auto-detection. Use for git commit, commit changes, save work, stage and commit.
prompt
Create or optimize prompts using best practices.
watch
Check for Claude Code updates, detect breaking changes, analyze plugin compatibility, and optionally gather community pulse via Exa.
design-audit
Audit an existing HTML/CSS design. Deterministic checks only (contrast, fonts, colors, states, dark mode) plus a visual pass. No generation.
fix-pr-comments
Systematically resolve Pull Request review comments using gh CLI to fetch comments and apply requested changes.
amend
Amend last commit safely. Use for amend, fix last commit, update commit, modify commit.