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 mendixlabs/mxcli --skill graph-analysisgit clone --depth 1 https://github.com/mendixlabs/mxcliWrote 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/mendixlabs/mxcli/graph-analysis)<a href="https://agentmods.dev/skills/mendixlabs/mxcli/graph-analysis"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/graph-analysis/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/mendixlabs/mxcli/graph-analysis"><img src="https://agentmods.dev/badge/skills/mendixlabs/mxcli/graph-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.04065 |
| Opus 5.5 | $0.00020 | $0.01626 |
| Sonnet 5.5 | $0.00010 | $0.00813 |
| Haiku 4.5 | $0.00005 | $0.00407 |
Grade A, and why
graph-analysis 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 5d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find it fast
sed -n '<from>,<to>p' SKILL.md one section rather than reading the file;
./mxcli syntax <topic> answers how do I write this for a fraction of either.
| lines | section |
|---|---|
| 32-41 | When to Read This Skill |
| 42-77 | Setup: Two-Step Refresh |
| 78-112 | Use Case 1: Pre-Change Impact Assessment |
| 113-139 | Use Case 2: Dead Code Identification |
| 140-178 | Use Case 3: Module Health (Cohesion & Coupling) |
| 179-210 | Use Case 4: Community Analysis (Bounded Context Validation) |
| 211-239 | Use Case 5: Finding Bridges (Centrality) |
| 240-253 | Use Case 6: Entity Hotspots |
| 254-299 | Use Case 7: Dependency Cycles |
| 300-331 | Use Case 8: Monolith-to-Multi-App Planning |
| 332-347 | Topological Layer Reference |
| 348-367 | Quick Reference: Which Table Answers What |
| 368-373 | Related Skills |
Graph Analysis: Impact Assessment & Architecture Evaluation
Use this skill when assessing the impact of a change, identifying risky elements, evaluating module health, or planning a structural refactor. The graph tables model the entire project as a dependency graph and expose topology metrics on top of it.
When to Read This Skill
- Before modifying an entity or microflow that might be widely used
- Before moving elements between modules
- When assessing architectural health (coupling, cohesion, god nodes)
- When planning to split a module or extract a bounded context
- When identifying dead code to remove
Setup: Two-Step Refresh
Two separate commands are needed. The full catalog must exist before community detection runs.
# Step 1: Build the full catalog (activities, widgets, cross-references)
# Skip if already fresh — check .mxcli/catalog.db mtime
./mxcli -p app.mpr -c "REFRESH CATALOG FULL"
# Step 2: Run graph algorithms (community detection, centrality, layers, cycles)
./mxcli -p app.mpr -c "REFRESH CATALOG COMMUNITIES"
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.
- 5d ago Changed · +22 lines 5b569c2d97be
- 15d ago Changed bd7782f5fc28
- 16d ago Changed 84ebd529e6f1
- 1mo ago Changed · +42 lines 9417f68f906d
- 1mo ago First seen · 310 lines · 50 tokens per session scan A 0793fc59f895
graph-analysis is a skill published in the GitHub repository mendixlabs/mxcli (131 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 4,065 once invoked, about $0.0002 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.
Other skills, from other repositories
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.