dag-map
Render the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API. Cross-checks the orchestration dataset against the raw agent records and session detail. Use when visualizing how a session's agent structure was organized.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill dag-map --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.
# DAG Map Render the subagent orchestration graph for one Claude Code session as a depth-ordered DAG. ## Input The user provides: **$ARGUMENTS** A session ID. If empty, fetch `GET /api/sessions?limit=1` and use the most recent session, stating which one you picked. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/workflows/{sessionId}` | The `orchestration` dataset: DAG nodes (agent id, type, model, status, depth) and parent→child edges | | `GET /api/agents` | Raw subagent records (`status`, `type`, `depth`, `parent`) to cross-check node/edge counts | | `GET /api/sessions/{sessionId}` | Full session detail with nested `agents[]` to confirm the root and total agent count | ## Report Sections ### 1. Topology Summary From `orchestration`: the root agent, total agent count, max depth, and max fan-out (most children under any one parent). Confirm the agent count against `/api/agents` filtered to this session. ### 2. Edge List Every parent→child edge, grouped by depth, formatted as: `depth d: parent[model] → child[type, status]` Mark leaf agents (no children) and any orphan nodes (a `parent` that is not present in the node set). ### 3. Depth & Fan-out Table | Dep
- Input
- Data Sources
- Report Sections
- 1. Topology Summary
- 2. Edge List
- 3. Depth & Fan-out Table
- 4. ASCII Tree
- Output
What does the dag-map skill do?
Render the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API. Cross-checks the orchestration dataset against the raw agent records and session detail. Use when visualizing how a session's agent structure was organized.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill dag-map --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.