centrality-analysis

centrality-analysis is a skill for Claude Code, Codex from MattArtzAnthro/gephi-ai. It costs 53 tokens per session (1,226 once invoked), scanned A, original, Apache-2.0.

A workflow for measuring which nodes matter most in a network loaded in Gephi, a desktop tool for exploring connected data. It compares several measures, such as direct connections, links between groups, and importance from influential neighbors.

In plain words
What is it for?
Use it to find highly connected nodes, nodes that link otherwise separate groups, influential nodes, and possible weak points in a network.
Why use it?
It prevents different meanings of “important” from being mixed together. You can see whether a node is a hub, a bridge, or influential for another reason.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find highly connected nodes, nodes that link otherwise separate groups, influential nodes, and possible weak points in a network.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mattartzanthro/gephi-ai/centrality-analysis
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 MattArtzAnthro/gephi-ai --skill centrality-analysis
Clone the repo
git clone --depth 1 https://github.com/MattArtzAnthro/gephi-ai

Made for: Claude Code, Codex.

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 centrality-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/mattartzanthro/gephi-ai/centrality-analysis/github.svg)](https://agentmods.dev/skills/mattartzanthro/gephi-ai/centrality-analysis)
Your own site
<a href="https://agentmods.dev/skills/mattartzanthro/gephi-ai/centrality-analysis"><img src="https://agentmods.dev/badge/skills/mattartzanthro/gephi-ai/centrality-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.

agentmods 80×15 button for centrality-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/mattartzanthro/gephi-ai/centrality-analysis"><img src="https://agentmods.dev/badge/skills/mattartzanthro/gephi-ai/centrality-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,226 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.00053 $0.01226
Opus 5.5 $0.00021 $0.00490
Sonnet 5.5 $0.00011 $0.00245
Haiku 4.5 $0.00005 $0.00123

Measured 28d ago against content hash 5453ad885c7a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

centrality-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 28d 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.

plugins/gephi-network-analysis/skills/centrality-analysis/SKILL.md · 56 lines

How it starts

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

Centrality Analysis Workflow

Run comprehensive centrality analysis to identify the most important and influential nodes in the graph.

Follow the gephi skill's rules throughout; this workflow repeats only the ones it is most likely to break. Read ../gephi/references/statistics-guide.md before interpreting scores, and ../gephi/references/layout-guide.md before the layout step.

Tell the user what you are doing at each step. Narrate briefly before each tool call.

Rules this workflow must keep

  • Session start. Start with gephi_health_check. Then check which workspace is open (gephi_list_workspaces) and whether a filter is active (filter_active in replies): a filter from an earlier conversation stays on, and exports and checks then see only what it shows.
  • Ranking. To rank nodes on a metric, call gephi_query_nodes with sort_by set to the metric, columns set to the few columns you need, and limit about 10: nodes are ordered before paging, so the first page is the top of the whole graph. Without columns, every attribute of every node comes back and a long listing can overflow.
  • No scale-free label. Never call a heavy-tailed degree distribution "scale-free" or a "power law": those fits are near-indistinguishable from log-normal in practice and smuggle in a universal-law claim (Jacomy 2020; Broido and Clauset 2019). Describe hub dominance as a property of this network.
  • Eigenvector caveat. Gephi's eigenvector centrality can rank nodes differently from a standard calculation. Never rank on it alone: compare it with PageRank, and report a node as an authority only when the two agree.

Steps

  1. Session start: Call gephi_health_check. If it fails, tell the user to start Gephi and stop. Call gephi_list_workspaces and gephi_get_project_info for node and edge counts and graph type. If filter_active is true, say that the scores will describe only the visible nodes.

  2. Compute all centrality metrics:

    • Call gephi_compute_degree for degree (number of ties)
    • Call gephi_compute_betweenness for betweenness centrality (how often a node sits on the shortest path between others), closeness, and eccentricity
    • Call gephi_compute_pagerank for PageRank (importance passed on by important neighbours)
    • Call gephi_compute_eigenvector for eigenvector centrality (ties to well-tied nodes)

Read the full file on GitHub · 56 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. 28d ago Changed · +11 lines 5453ad885c7a
  2. 1mo ago First seen · 45 lines · 53 tokens per session scan A 86f38fbcbad5

Subscribe to this mod's changes

centrality-analysis is a skill published in the GitHub repository MattArtzAnthro/gephi-ai (25 stars, last pushed 12d ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,226 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.