How do I install the Dag Map skill?

Run npx skillmds@latest add hoangsonww/dag-map in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dag Map safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dag Map?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dag Map free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dag Map?

hoangsonww (@hoangsonww) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dag Map by hoangsonww — Agent Skill

Name: Dag Map
Rating: 4.2 (5 reviews)
Author: hoangsonww

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.

hoangsonww Updated Sep 10, 2026

File contents

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

Depth	Agents at depth	Children spawned	Avg fan-out

4. ASCII Tree

A simple indented tree rendering of the DAG, e.g.:

root [opus, completed]
├─ explore [sonnet, completed]
└─ code-review [sonnet, error]
   └─ debugger [sonnet, completed]

Output

Render as Markdown tables plus one fenced ASCII tree block.
Cite real node and edge counts from the API — never invent agents or edges.
If a session has no subagents, say so plainly (single-agent session, depth 0) instead of fabricating a tree.
If the dashboard is unreachable, tell the user to start it with npm start from the repo root.

---name: dag-mapdescription: 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.---# DAG MapRender the subagent orchestration graph for one Claude Code session as a depth-ordered DAG.## InputThe 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 SummaryFrom `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 ListEvery 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| Depth | Agents at depth | Children spawned | Avg fan-out ||-------|-----------------|------------------|-------------|### 4. ASCII TreeA simple indented tree rendering of the DAG, e.g.:```root [opus, completed]├─ explore [sonnet, completed]└─ code-review [sonnet, error] └─ debugger [sonnet, completed]```## Output- Render as Markdown tables plus one fenced ASCII tree block.- Cite real node and edge counts from the API — never invent agents or edges.- If a session has no subagents, say so plainly (single-agent session, depth 0) instead of fabricating a tree.- If the dashboard is unreachable, tell the user to start it with `npm start` from the repo root.

Frequently asked questions