dependency-graph

dependency-graph is a skill for Claude Code from DavidROliverBA/ArchitectKB. It costs 10 tokens per session (2,014 once invoked), scanned A, original, MIT.

A way to map how systems depend on one another and display those relationships as text, ASCII art, Mermaid, or D3. A dependency is a relationship where one system needs another to work.

In plain words
What is it for?
Use it to trace upstream sources or downstream users, inspect a selected number of dependency levels, assess risks, plan maintenance, or prepare disaster-recovery work.
Why use it?
It shows what could be affected by an outage, change, or system removal and helps reveal bottlenecks and single points of failure.

Skill for Claude Code

Written for Claude Code: context: fork in frontmatter. Also seen: model in frontmatter.

Good fit Use it to trace upstream sources or downstream users, inspect a selected number of dependency levels, assess risks, plan maintenance, or prepare disaster-recovery work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davidroliverba/architectkb/dependency-graph
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 DavidROliverBA/ArchitectKB --skill dependency-graph
Clone the repo
git clone --depth 1 https://github.com/DavidROliverBA/ArchitectKB

Made for: Claude Code.

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 dependency-graph

README.md
[![agentmods](https://agentmods.dev/badge/skills/davidroliverba/architectkb/dependency-graph/github.svg)](https://agentmods.dev/skills/davidroliverba/architectkb/dependency-graph)
Your own site
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/dependency-graph"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/dependency-graph/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 dependency-graph

Your own site · 80×15
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/dependency-graph"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/dependency-graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,014 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.00010 $0.02014
Opus 5.5 $0.00004 $0.00806
Sonnet 5.5 $0.00002 $0.00403
Haiku 4.5 $0.00001 $0.00201

Measured 1mo ago against content hash f528992e5ec9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dependency-graph 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 1mo 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.

.claude/skills/dependency-graph/SKILL.md · 269 lines

How it starts

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

/dependency-graph Skill

Visualize system dependencies and identify critical paths, bottlenecks, and single points of failure.

When to Use This Skill

Use /dependency-graph when you need to:

  • Understand what systems depend on a critical system
  • Identify single points of failure
  • Plan outage impact for maintenance
  • Design disaster recovery strategies
  • Perform risk assessment on architecture
  • Plan system decommissioning (understand what breaks)
  • Optimize architecture to reduce critical dependencies

Usage

/dependency-graph [root-system] [options]

Parameters

Parameter Description Required
root-system System to analyze (or "all" for enterprise graph) Optional
--depth How many hops to follow (1=direct, 2=direct+indirect, all) Optional
--direction Direction to follow (upstream=sources, downstream=consumers, both) Optional
--visualization Graph format (text, ascii-art, mermaid, d3) Optional

Workflow

Phase 1: Define Graph Scope

User specifies:

  1. Root system (optional - default: all systems)

    • Single system (system:ERP)
    • All systems (enterprise)
    • Critical systems only
  2. Depth (optional)

    • 1 - Direct dependencies only (immediate consumers/producers)
    • 2 - Direct + indirect (one level deeper)
    • all - All paths to edges (complete dependency closure)
  3. Direction (optional)

    • upstream - What feeds into this system (sources)
    • downstream - What consumes from this system
    • both - Both upstream and downstream (default)
  4. Visualization (optional)

    • text - ASCII text representation
    • ascii-art - Fancy ASCII visualization
    • mermaid - Mermaid diagram (for markdown)
    • d3 - Interactive D3 visualization (HTML)

Phase 2: Analyze Dependencies

The skill:

  1. Builds dependency graph
    • Reads all Integration notes
    • Maps directional relationships
    • Calculates paths and cycles

Read the full file on GitHub · 269 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. 1mo ago First seen · 269 lines · 10 tokens per session scan A f528992e5ec9

Subscribe to this mod's changes

dependency-graph is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (53 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 2,014 once invoked, about $0.0000 per session on Opus 5.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-30.

Related

Other skills, from other repositories

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

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 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

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens