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 agentmods add skills/davidroliverba/architectkb/dependency-graphnpx skills add DavidROliverBA/ArchitectKB --skill dependency-graphgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/dependency-graph)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/dependency-graph"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/dependency-graph.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.02014 |
| Opus 5 | $0.00005 | $0.01007 |
| Sonnet 5 | $0.00002 | $0.00403 |
| Haiku 4.5 | $0.00001 | $0.00201 |
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 4d 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 — 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:
-
Root system (optional - default: all systems)
- Single system (system:ERP)
- All systems (enterprise)
- Critical systems only
-
Depth (optional)
1- Direct dependencies only (immediate consumers/producers)2- Direct + indirect (one level deeper)all- All paths to edges (complete dependency closure)
-
Direction (optional)
upstream- What feeds into this system (sources)downstream- What consumes from this systemboth- Both upstream and downstream (default)
-
Visualization (optional)
text- ASCII text representationascii-art- Fancy ASCII visualizationmermaid- Mermaid diagram (for markdown)d3- Interactive D3 visualization (HTML)
Phase 2: Analyze Dependencies
The skill:
- Builds dependency graph
- Reads all Integration notes
- Maps directional relationships
- Calculates paths and cycles
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.
- 4d ago First seen · 269 lines · 10 tokens per session scan A f528992e5ec9
dependency-graph is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 2,014 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…