fleet-runs SKILL.md skillA
fleet-runs from hoangsonww/claude-code-agent-monitor is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hoangsonww/claude-code-agent-monitor/fleet-runs@git:20260804.9eab0d7Pins git:20260804.9eab0d7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hoangsonww/claude-code-agent-monitor
- Path
plugins/ccam-workflows/skills/fleet-runs/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260804.9eab0d7, committed Aug 4, 2026
- First version recorded
- Jun 25, 2026
- Size
- 2,549 bytes
- Repository stars
- 1,159
- License
- MIT
Summarize Workflow-tool fleet runs from the Agent Monitor — these fleets emit no hooks and are ingested from on-disk run journals. List recent runs with status and agents-per-run, then drill into a single run's per-agent detail. Reconciles against the live run-state endpoints. Use when reviewing Workflow() fleets rather than hook-instrumented interactive sessions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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)
…Read the whole file at its exact version.
How to install
mdr add hoangsonww/claude-code-agent-monitor/fleet-runs@sha256:7b745ebaafdae729The line at the top of this page pins the label git:20260804.9eab0d7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_w57t4lxvbga6vla6)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 25, 2026 and Aug 4, 2026, about one every 41 days. Its first recorded version is graded B and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.9eab0d7 latest | 2026-08-04 | 9eab0d7 | 2,549 B | A | view · diff |
| git:20260625.879bbc2 | 2026-06-25 | 879bbc2 | 2,532 B | B | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2549 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hoangsonww/claude-code-agent-monitor · 1,159 stars · license MIT · pushed 2026-11-08 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_w57t4lxvbga6vla6 GET https://markdownregistry.com/api/v1/resolve?ref=hoangsonww/claude-code-agent-monitor/fleet-runs GET https://markdownregistry.com/api/v1/blob/7b745ebaafdae729fcd73e33f9919014f68a238701f9ecd1e7f9b3342370a041
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.