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.
git 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/commands/mattartzanthro/gephi-ai/import-and-explore)<a href="https://agentmods.dev/commands/mattartzanthro/gephi-ai/import-and-explore"><img src="https://agentmods.dev/badge/commands/mattartzanthro/gephi-ai/import-and-explore.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.00013 | $0.00674 |
| Opus 5 | $0.00006 | $0.00337 |
| Sonnet 5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
import-and-explore 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import & Explore
Import a graph file into Gephi, run initial analysis, apply styling, and present an overview.
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. -
Create project: Call
gephi_create_projectto start fresh. -
Import file: Call
gephi_import_filewith the path from$ARGUMENTS. Support GEXF, GraphML, GML, CSV, DOT, and Pajek formats. -
The intake question (skip if they already told you): in one friendly question, ask what the nodes and connections are and what they hope to learn. Their answer sets the vocabulary for everything you present, and their expectations become hypotheses to test rather than assumptions.
-
Profile: Call
gephi_profile_graph(one call, the full quantitative picture). Give a short plain-language first reading that combines their description with the numbers, then ask the two or three questions the profile raises (itsflagsare candidates: isolates, fragmentation, hub dominance). -
Let the intake + profile guide what follows — do not run a fixed recipe:
- Isolates or fragmentation: ask before removing anything (their "data problem" may be their finding).
- Their stated interest picks the metric (brokers/gatekeepers -> betweenness; influence/reach -> degree or PageRank; roles -> the similarity layout).
- If they named an attribute they expect to organize the network, test it against the partition baseline before coloring by it; prefer detected communities when their attribute fails, and say so plainly.
- Size and density pick the layout per the layout guide's purpose table.
- Caption clusters in their vocabulary, not in cluster numbers.
-
Style the graph (guided by the above):
- Color by community:
gephi_color_by_partitionwith column"modularity_class"and the validated palette (see skill reference) - Size by degree:
gephi_size_by_rankingwith column"degree", min_size 3, max_size 25
- Color by community:
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 · 58 lines · 13 tokens per session scan A dab0ade75c6f
import-and-explore is a command published in the GitHub repository MattArtzAnthro/gephi-ai (22 stars, last pushed 7d ago), licensed Apache-2.0. It adds 13 tokens to every session and 674 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 commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
README
Git workflow and quality assurance commands for the claude-skills repository.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
growth-seo
SEO audit and optimization for organic search ranking.
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.