A command that prints a quick snapshot of Claude Code completion, tool success, and error rates. An SLO is a target for how reliably a service should work.

Use it to check session completion, tool success, and API error rates against default targets.

It replaces manual calculations with a small report showing which reliability targets are met or missed.

slo — Command for Claude Code by hoangsonww

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/hoangsonww/Claude-Code-Agent-Monitor

Made for: Claude Code.

Or install ccam-quality, the plugin that ships this one along with the rest of its 5 skills, 3 commands, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/slo/github.svg)](https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/slo)

Your own site

<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/slo"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/slo/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/hoangsonww/claude-code-agent-monitor/slo"><img src="https://agentmods.dev/badge/commands/hoangsonww/claude-code-agent-monitor/slo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 369 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00369
Opus 5	$0.00009	$0.00185
Sonnet 5	$0.00003	$0.00074
Haiku 4.5	$0.00002	$0.00037

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

Security

Grade A, and why

slo 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/analytics

plugins/ccam-quality/commands/slo.md · 32 lines

What it actually says

Print a compact SLO snapshot for Claude Code usage from the Agent Monitor dashboard at http://localhost:4820. No arguments.

Fetch the raw counts:
```
curl -s http://localhost:4820/api/analytics
curl -s http://localhost:4820/api/stats
```
From analytics: event_types (PreToolUse, PostToolUse, APIError) and sessions_by_status. From stats: total_events, total_sessions.
Compute three SLIs:
- Completion rate = completed sessions / total sessions (from sessions_by_status; exclude still-active/running sessions from the denominator).
- Tool success rate = PostToolUse / PreToolUse (cap at 100%).
- Error rate = APIError / total_events.
Compare each to its default target (completion ≥ 95%, tool success ≥ 99%, error ≤ 1%) and print one line per SLI: SLI .......... observed% (target X%) ✅ MET | ❌ BREACHED

Output rules: rates as percentages to 2 decimals; cite only fields the API returned — never fabricate. End with one verdict line (e.g., SLOs: 3/3 met or SLOs: error rate BREACHED). Keep it to the snapshot only; no extra prose. If curl cannot reach http://localhost:4820, tell the user to start the dashboard with npm start from the repo root.

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.

8d ago First seen · 32 lines · 17 tokens per session scan A 54437ca64c24

Subscribe to this mod's changes

slo is a command published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (989 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 369 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.

Analytics and metrics Claude Code Debugging claude-agents claude-skills express expressjs node

slo

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Makes network callslowCapability

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

deep-code-analysis

watch

fix

fix-zh

apex

explain-architecture