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 MattArtzAnthro/gephi-ai --skill centrality-analysisgit clone --depth 1 https://github.com/MattArtzAnthro/gephi-aiWrote 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/mattartzanthro/gephi-ai/centrality-analysis)<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="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.1 | $0.00053 | $0.00574 |
| Opus 5 | $0.00026 | $0.00287 |
| Sonnet 5 | $0.00011 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00057 |
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 8d 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.
What it actually says
Centrality Analysis Workflow
Run comprehensive centrality analysis to identify the most important and influential nodes in the graph.
Read ../gephi/references/statistics-guide.md before interpreting scores.
Tell the user what you're doing at each step — narrate briefly before each tool call.
Steps
-
Health check: Call
gephi_health_check. If it fails, tell the user to start Gephi and stop. -
Graph info: Call
gephi_get_project_infoto get node/edge counts and graph type. -
Compute all centrality metrics:
- Call
gephi_compute_degreefor degree distribution - Call
gephi_compute_betweennessfor betweenness centrality, closeness, and eccentricity - Call
gephi_compute_pagerankfor PageRank importance - Call
gephi_compute_eigenvectorfor eigenvector centrality
- Call
-
Query top nodes: Call
gephi_query_nodeswith limit 100 to retrieve node data. Sort and identify:- Top 10 by degree (hubs)
- Top 10 by betweenness centrality (bridges)
- Top 10 by PageRank (importance)
- Nodes that appear in multiple top-10 lists (key actors)
-
Visualize by betweenness: Call
gephi_color_by_rankingwith:- column:
"betweenesscentrality" - Light blue to dark red gradient:
r_min: 200, g_min: 220, b_min: 255, r_max: 180, g_max: 0, b_max: 0
- column:
-
Size by PageRank: Call
gephi_size_by_rankingwith column"pageranks",min_size: 3,max_size: 30. -
Layout: Tell the user: "Running ForceAtlas 2 layout..." Call
gephi_run_layoutwith algorithm"ForceAtlas 2", 1000 iterations. -
Report: Present a ranked table of key nodes with their centrality scores. Highlight:
- Hubs: High degree nodes
- Bridges: High betweenness, low degree (connecting different communities)
- Authorities: High PageRank / eigenvector centrality
- Vulnerabilities: Nodes whose removal would fragment the network
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.
- 8d ago First seen · 45 lines · 53 tokens per session scan A 86f38fbcbad5
centrality-analysis is a skill published in the GitHub repository MattArtzAnthro/gephi-ai (22 stars, last pushed 7d ago), licensed Apache-2.0. It adds 53 tokens to every session and 574 once invoked, about $0.0003 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
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…