hierarchy-tree

hierarchy-tree is a skill for Claude Code from JoshuaRamirez/ms-ado-az-claude-code-plugin. It costs 77 tokens per session (909 once invoked), scanned A, original, MIT.

A method for drawing parent-and-child work items as an ASCII tree, using plain text characters. Work items are tracked pieces of work such as features, tasks, or epics.

In plain words
What is it for?
Showing feature hierarchies, parent-child relationships, and nested work items from Azure DevOps data.
Why use it?
A flat list of work items can hide which items belong under others; a tree makes those relationships easier to read.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the ado-work-items plugin — 5 skills, 2 commands, 1 agent shipped together

Good fit Showing feature hierarchies, parent-child relationships, and nested work items from Azure DevOps data.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/joshuaramirez/ms-ado-az-claude-code-plugin/hierarchy-tree
Install

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.

Any agent
npx skills add JoshuaRamirez/ms-ado-az-claude-code-plugin --skill hierarchy-tree
Clone the repo
git clone --depth 1 https://github.com/JoshuaRamirez/ms-ado-az-claude-code-plugin

Made for: Claude Code.

Or install ado-work-items, the plugin that ships this one along with the rest of its 5 skills, 2 commands, 1 agent.

Wrote 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.

agentmods badge for hierarchy-tree

README.md
[![agentmods](https://agentmods.dev/badge/skills/joshuaramirez/ms-ado-az-claude-code-plugin/hierarchy-tree/github.svg)](https://agentmods.dev/skills/joshuaramirez/ms-ado-az-claude-code-plugin/hierarchy-tree)
Your own site
<a href="https://agentmods.dev/skills/joshuaramirez/ms-ado-az-claude-code-plugin/hierarchy-tree"><img src="https://agentmods.dev/badge/skills/joshuaramirez/ms-ado-az-claude-code-plugin/hierarchy-tree/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.

agentmods 80×15 button for hierarchy-tree

Your own site · 80×15
<a href="https://agentmods.dev/skills/joshuaramirez/ms-ado-az-claude-code-plugin/hierarchy-tree"><img src="https://agentmods.dev/badge/skills/joshuaramirez/ms-ado-az-claude-code-plugin/hierarchy-tree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 909 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.00909
Opus 5 $0.00039 $0.00454
Sonnet 5 $0.00015 $0.00182
Haiku 4.5 $0.00008 $0.00091

Measured 9d ago against content hash 512c518d3fbd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

hierarchy-tree 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.

skills/hierarchy-tree/SKILL.md · 119 lines

How it starts

The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Building ASCII Trees from Parent/Child Data

When you have flat parent/child data, construct the tree visually using LLM reasoning - NO CODE NEEDED.

Step 1: Get the Data

Query work items with their parent:

az boards query --wiql "SELECT [System.Id], [System.Title] FROM workitems WHERE [System.WorkItemType] = 'Feature' AND [System.TeamProject] = 'ProjectName'" -o json

Then for each item, get its parent via relations (System.LinkTypes.Hierarchy-Reverse).

The result is flat data like:

ID     Parent   Title
1517   1509     Feature A
1518   1509     Feature B
1759   1827     Feature C
1827   1509     Feature D

Step 2: Build the Tree (LLM Reasoning)

  1. Find roots - Items whose Parent is not in the ID list (or is an Epic/external)
  2. Group children - For each ID, collect all items where Parent = that ID
  3. Recurse - Build subtrees for each child

From the example above:

  • Root: 1509 (not in ID list as a child)
  • 1509's children: 1517, 1518, 1827
  • 1827's children: 1759

Step 3: Render ASCII

Use these characters:

|   = vertical continuation (more siblings below)
|-- = branch to sibling (more siblings follow)
`-- = last branch (no more siblings)
    = indent (4 spaces under a last branch)

Rules:

  • Each level indents 4 characters
  • Use |-- for all children except the last
  • Use `-- for the last child
  • Continue | vertically when parent has more siblings

Example Transformation

Input data:

ID    Parent  Name
100   -       Root
200   100     Child A
300   100     Child B
400   300     Grandchild B1
500   300     Grandchild B2
600   100     Child C

Output tree:

#100 Root
|-- #200 Child A
|-- #300 Child B
|   |-- #400 Grandchild B1
|   `-- #500 Grandchild B2
`-- #600 Child C

Complex Example

Input:

ID    Parent  Name
1     -       Epic
10    1       Feature A
11    1       Feature B
20    10      Sub A1
21    10      Sub A2
30    11      Sub B1
31    30      Deep B1a
32    30      Deep B1b

Read the full file on GitHub · 119 lines

Changes

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.

  1. 9d ago First seen · 119 lines · 77 tokens per session scan A 512c518d3fbd

Subscribe to this mod's changes

hierarchy-tree is a skill published in the GitHub repository JoshuaRamirez/ms-ado-az-claude-code-plugin (5 stars, last pushed 6d ago), licensed MIT. It adds 77 tokens to every session and 909 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens