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 export-mapgit 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/export-map)<a href="https://agentmods.dev/skills/mattartzanthro/gephi-ai/export-map"><img src="https://agentmods.dev/badge/skills/mattartzanthro/gephi-ai/export-map/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/export-map"><img src="https://agentmods.dev/badge/skills/mattartzanthro/gephi-ai/export-map.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.00044 | $0.01353 |
| Opus 5.5 | $0.00018 | $0.00541 |
| Sonnet 5.5 | $0.00009 | $0.00271 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
export-map 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Export Map
Export the map currently open in Gephi: a clean PNG, a labeled PNG, an SVG, a
legend when colour encodes groups, and a copy-ready caption. This workflow
exports; it does not lay out or style. The map has to be a map first (laid out,
sized, colored), which the visualize-network workflow does.
Follow the gephi skill's rules throughout; this workflow repeats only the ones
it is most likely to break.
Read ../gephi/references/reading-network-maps.md for
the caption discipline.
Tell the user what you are doing at each step. Narrate briefly before each tool call so they know what is happening.
Rules this workflow must keep
- Asking. When a step says to ask, ask once. If the person cannot answer, is away, or asked for a finished product, use the default named in that step and remove or overwrite nothing. At the end, give one short line for each choice that changed the result, under "Choices I made"; leave the section out when every step used its obvious default. If there is no input to work on, stop and say what is needed.
- 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. - 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). - 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.
Steps
- Session start: Call
gephi_health_check. If it fails, tell the user to start Gephi and stop. Callgephi_list_workspacesandgephi_get_project_info. Tell the user the node and edge counts and which workspace will be exported. If the graph is empty, stop and tell them. Iffilter_activeis true, say that the export will show only the visible nodes, and put that in the caption.
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 · +16 lines f32ba176e33c
- 1mo ago First seen · 70 lines · 44 tokens per session scan A 41a3e740c63e
export-map is a skill published in the GitHub repository MattArtzAnthro/gephi-ai (25 stars, last pushed 12d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,353 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
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.