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.
Install / Use
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill endpoint-probeInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of endpoint-probe
endpoint-probe scores 81/100 on our quality scale, 2375th of 2,758 Automation skills we index.
Its SKILL.md is 2.9 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.
With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so endpoint-probe is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
endpoint-probe compared with similar skills
All 4 of these similar skills score higher than endpoint-probe; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| endpoint-probe (this skill)by hoangsonww | 81 | 1.0k | 2mo ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 114.0k | today | CLAUDE.md |
| rufloby ruvnet | 100 | 82.3k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 80.5k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 40.6k | 12d ago | CLAUDE.md |
Frequently asked questions
- How do I install endpoint-probe?
- Run
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill endpoint-probe. The install tabs above show the steps for each supported agent. - Which AI agents does endpoint-probe work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is endpoint-probe safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is endpoint-probe still maintained?
- The repository was last updated about 2 months ago, so endpoint-probe is actively maintained.
Skill content
View source on GitHubname: endpoint-probe description: > 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.
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, commands, plugins, mcp, hooks, etc.) |
Method
For each route, issue a single GET against http://localhost:4820<path> with a
short timeout, capturing the HTTP status code, round-trip latency, and the
top-level shape of the JSON body (object keys, or array length). A route counts
as reachable when it returns a 2xx with parseable JSON.
If /api/stats itself fails to connect, the dashboard is not running — stop and
tell the user to start it with npm start (or npm run dev) from the repo root.
Report Sections
1. Probe Matrix
A Markdown table — one row per route — with columns:
endpoint, status (HTTP code), latency, reachable (✅/❌), shape
(e.g. object: {total_cost, breakdown[…]} or array[N]).
2. Reachability Summary
Count of reachable vs total. Name any unreachable or non-2xx routes explicitly.
3. Verdict
One line: install looks healthy (all reachable) or partially wired (list the gaps and the most likely cause — server not running, route disabled, or empty data).
Output
- Compact Markdown; the probe matrix is the centerpiece.
- Cite the real status code, latency, and observed shape per route — never assume.
- Report shape from what actually came back; if a route returns an empty array or object, say so rather than inferring fields.
- Keep currency, where shown, to 4 decimals (e.g.
total_cost: $0.0000).
Related Skills
Agent-Reach
114.0kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
82.3k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
80.5kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Claude-Code-Game-Studios
40.6kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
