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 danielrosehill/Claude-Taxonomy-Creation-Plugin --skill hierarchical-taxonomiesgit clone --depth 1 https://github.com/danielrosehill/Claude-Taxonomy-Creation-PluginWrote 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/danielrosehill/claude-taxonomy-creation-plugin/hierarchical-taxonomies)<a href="https://agentmods.dev/skills/danielrosehill/claude-taxonomy-creation-plugin/hierarchical-taxonomies"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-taxonomy-creation-plugin/hierarchical-taxonomies/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/danielrosehill/claude-taxonomy-creation-plugin/hierarchical-taxonomies"><img src="https://agentmods.dev/badge/skills/danielrosehill/claude-taxonomy-creation-plugin/hierarchical-taxonomies.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00032 | $0.00645 |
| Opus 5 | $0.00016 | $0.00322 |
| Sonnet 5 | $0.00006 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
hierarchical-taxonomies 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 12d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hierarchical Taxonomies
Generate and structure a parent/child taxonomy tree. Choose storage schema, validate the hierarchy, export in multiple formats.
When to use
- "Create a product category tree"
- "I need a nested content classification with subcategories"
- "Build a Dewey-style organizational hierarchy"
- "Generate a category / subcategory taxonomy for…"
Inputs to gather
- Domain: What is this hierarchy for?
- Depth: How deep? (2–3 levels typical; >5 is rare)
- Branching factor: Rough average children per node?
- Root: Is there a single root node or multiple top-level categories?
- Schema preference: How to store parent/child relationships?
Procedure
- Recommend schema: Default to adjacency list (id, parent_id, code, label, description) for most cases (≤10k nodes, simple queries). For deep lookups or range queries, suggest:
- Materialized path (
/electronics/computers/laptops): good for traversal; update-heavy if paths change. - Nested set (lft, rgt): efficient range queries; complex to maintain; only if user explicitly asks.
- Materialized path (
- Elicit spec using the pattern from
generate-from-spec: domain, scope, depth, fields. - Generate the hierarchy:
- Build a tree structure with each node having: code (PK, unique), label, description, parent_code (nullable for roots).
- For small/standard hierarchies: write directly.
- For large/specialized: suggest web research or external source (e.g., existing open taxonomies).
- Validate the tree:
- Ensure every
parent_coderesolves to an existing code (no dangling FKs). - Detect cycles via depth-first search; fail loudly if found.
- Check all nodes are reachable from root(s); warn if islands exist.
- Ensure every
- Output:
data/<name>/<name>.csv: Flat adjacency-list format (code, parent_code, label, description).data/<name>/tree.json: Nested JSON tree for human review (each node has children array).data/<name>/<name>-materialized-paths.csv(optional): Addpathcolumn for materialized-path schema if user requests.
- Show tree.json to user for review before load.
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.
- 12d ago First seen · 55 lines · 32 tokens per session scan A 35823161db4d
hierarchical-taxonomies is a skill published in the GitHub repository danielrosehill/Claude-Taxonomy-Creation-Plugin (3 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 645 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…