endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill endpoint-probe --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Endpoint Probe Smoke-test the dashboard's main API surface by hitting each major route once and reporting whether it responds and what shape it returns. ## Input The user provides: **$ARGUMENTS** Options: empty (default: probe all routes below), or a substring to filter which routes are probed (e.g. `pricing` probes only matching routes). ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/stats` | `{ total_sessions, active_sessions, active_agents, total_agents, total_events, events_today, ws_connections, agents_by_status, sessions_by_status }` | | `GET /api/analytics` | `{ overview, tokens, tool_usage, daily_events, daily_sessions, agent_types, event_types, avg_events_per_session, total_subagents, sessions_by_status, agents_by_status }` | | `GET /api/sessions` | Session list; each: `id, status, model, cwd, started_at, ended_at, cost, metadata` | | `GET /api/pricing/cost` | `{ total_cost, breakdown:[{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] }` | | `GET /api/workflows/runs` | Workflow-tool run journals (fleets) | | `GET /api/cc-config/overview` | Claude Code config explorer overview (skills, agents, com
- Input
- Data Sources
- Method
- Report Sections
- 1. Probe Matrix
- 2. Reachability Summary
- 3. Verdict
- Output
What does the endpoint-probe skill do?
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill endpoint-probe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.