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 skills add hoangsonww/Claude-Code-Agent-Monitor --skill fleet-runsgit 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/skills/hoangsonww/claude-code-agent-monitor/fleet-runs)<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/fleet-runs"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/fleet-runs/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/skills/hoangsonww/claude-code-agent-monitor/fleet-runs"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/fleet-runs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.00630 |
| Opus 5 | $0.00039 | $0.00315 |
| Sonnet 5 | $0.00016 | $0.00126 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
fleet-runs 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 9d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Runs
Summarize Workflow-tool (Workflow()) fleet runs and drill into one run's agents.
Input
The user provides: $ARGUMENTS
- Empty → list the most recent fleet runs.
- A run ID → drill into that single run.
latest→ drill into the most recent run.
These fleets emit no hooks; the dashboard ingests them from on-disk Workflow-tool run journals, so this data is independent of the hook event stream.
Data Sources
| Endpoint | Returns |
|---|---|
GET /api/workflows/runs |
List of ingested fleet run journals: run id, status, agent count, timing |
GET /api/workflows/runs/{runId} |
One run in detail: per-agent status, timing, type, and outputs |
GET /api/run |
Live run state across the fleet (current/active runs) |
GET /api/run/{id} |
Live state for one run, to reconcile against the journal |
Report Sections
1. Runs Overview (when listing)
| Run ID | Status | Agents | Started | Duration |
|---|---|---|---|---|
Sort most recent first. Add a one-line status mix below (e.g. 8 runs: 5 completed, 2 running, 1 error). |
2. Run Detail (when a run ID / latest is given)
From GET /api/workflows/runs/{runId}, reconciled with GET /api/run/{id}:
- Header: run id, status, total agents, wall-clock duration.
- Per-agent table:
Agent Type Status Duration Notes - Call out the longest-running agent and any agent with an error/failed status.
3. Status & Health
Completion rate (completed / total agents), any stalled or errored agents, and whether the journal and the live run-state endpoint agree (flag drift if they do not).
Output
- Markdown tables; status mix as a single summary line.
- Durations in human units (e.g.
3m 04s). - Make explicit that these runs come from run journals (no hooks), so hook-derived metrics do not apply.
- Cite only runs and agents returned by the API; never invent runs.
- If there are no fleet runs, say so plainly.
- If the dashboard is unreachable, tell the user to start it with
npm startfrom the repo root.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 60 lines · 78 tokens per session scan A 7b745ebaafda
fleet-runs is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 4d ago), licensed MIT. It adds 78 tokens to every session and 630 once invoked, about $0.0004 per session on Opus 5. 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-09-03.
Other skills, from other repositories
code-remediate
Apply selected review fixes; bare PR targets use current online items, while PR +review adds the latest matching artifact.
nodejs-expert
Expert-level Node.js backend development with Express, async patterns, streams, performance optimization, and production best practices. Use when the user mentions JavaScript, backend, Express, or async, or when the task involves Modern Node.js Features, Express Framework, File System Operations, or HTTP Requests.
assess
Analyze issue/PR/problem before implementation; produce source-backed findings and measurable gates.
optimize
Optimize a measurable metric with bounded iterations, guardrails, and regression gates.
react-tanstack-router
Use when implementing routing in a React app (NOT Next.js) with TanStack Router — file-based routes, loaders, search params.
laravel-blade
Create Blade templates with components, slots, layouts, and directives. Use when building views, reusable components, or templating.