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 visualize-networkgit 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/visualize-network)<a href="https://agentmods.dev/skills/mattartzanthro/gephi-ai/visualize-network"><img src="https://agentmods.dev/badge/skills/mattartzanthro/gephi-ai/visualize-network/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/mattartzanthro/gephi-ai/visualize-network"><img src="https://agentmods.dev/badge/skills/mattartzanthro/gephi-ai/visualize-network.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.01284 |
| Opus 5.5 | $0.00022 | $0.00514 |
| Sonnet 5.5 | $0.00011 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
visualize-network 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visualize a Network
Style and lay out the live graph in place. The goal is a map where real structure is visible, hubs are legible, edges are informative but quiet, and nothing is accidentally invisible.
Follow the gephi skill's rules throughout; this workflow repeats only the ones
it is most likely to break. Read ../gephi/references/layout-guide.md for layout
selection and its symptom-to-fix table. Read
../gephi/references/reading-network-maps.md for the caption and interpretation
discipline.
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_activein replies): a filter from an earlier conversation stays on, and exports and checks then see only what it shows. - Stability. Run
gephi_community_stabilitybefore naming, captioning, or colouring by groups, and say how stable they are. - Palette. On a light background, leave
colorsunset: the plugin gives the largest group the first of eight colours validated for readability, the next largest the second, and so on, in an order that keeps the five largest groups distinguishable wherever they touch, even for colour-blind readers; past five groups, label the groups as well. On a dark background, pass the dark-surface palette. Colour must never be the only way to tell groups apart: label the largest nodes or the groups. Dark-surface palette, keyed largest group first:{"0":[57,135,229],"1":[201,133,0],"2":[0,131,0],"3":[213,81,129],"4":[144,133,233],"5":[230,103,103],"6":[25,158,112],"7":[217,89,38]} - Edges. On a light background, edges use
{"edge.color": "#D0D0D0", "edge.opacity": 90, "edge.thickness": 1.0, "edge.curved": false}. Label settings change labels only; they never reset edge values. - Caption and legend. Every export ships with a copy-ready caption (data, layout and settings, what size and colour encode, what the map does and does not show) and, when colour encodes groups, a legend (
gephi_export_legend).
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.
- 28d ago Changed · +18 lines eccabde54b07
- 1mo ago First seen · 60 lines · 56 tokens per session scan A 22095c94e54a
visualize-network is a skill published in the GitHub repository MattArtzAnthro/gephi-ai (25 stars, last pushed 12d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,284 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
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
evo2-nim
Generate and analyze DNA sequences using NVIDIA's Evo 2 BioNeMo NIM microservice. Use for Evo2/Evo 2, DNA generation, genomic sequence generation, hosted generation, local Docker deployment, local forward passes, layer outputs, logits, sampled probabilities, and BioNeMo NIM workflows.