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 agentmods add skills/wentorai/research-plugins/network-visualization-guidenpx skills add wentorai/research-plugins --skill network-visualization-guidegit clone --depth 1 https://github.com/wentorai/research-pluginsWhat 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 | $0.00018 | $0.01467 |
| Opus 5 | $0.00009 | $0.00733 |
| Sonnet 5 | $0.00004 | $0.00293 |
| Haiku 4.5 | $0.00002 | $0.00147 |
Grade A, and why
network-visualization-guide 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 2d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Visualization Guide
A skill for visualizing networks, graphs, and relational data in research. Covers NetworkX for analysis, layout algorithms, publication-quality styling, and tools for citation networks, social networks, and knowledge graphs.
Network Basics
When to Use Network Visualization
Network visualization is appropriate when your data involves relationships:
- Citation networks (papers citing other papers)
- Co-authorship networks (researchers who collaborate)
- Social networks (individuals connected by interactions)
- Biological networks (protein interactions, gene regulation)
- Knowledge graphs (concepts linked by relationships)
- Trade/flow networks (countries, organizations, resources)
Key Concepts
Nodes (vertices): The entities in your network
Edges (links): The relationships between entities
Directed: Edges have direction (A -> B)
Undirected: Edges are bidirectional (A -- B)
Weighted: Edges have a strength or value
Building Networks with NetworkX
Creating and Analyzing a Network
import networkx as nx
def build_citation_network(citations: list[tuple]) -> dict:
"""
Build and analyze a citation network.
Args:
citations: List of (citing_paper, cited_paper) tuples
"""
G = nx.DiGraph()
G.add_edges_from(citations)
metrics = {
"n_nodes": G.number_of_nodes(),
"n_edges": G.number_of_edges(),
"density": nx.density(G),
"most_cited": sorted(
G.in_degree(), key=lambda x: x[1], reverse=True
)[:10],
"most_citing": sorted(
G.out_degree(), key=lambda x: x[1], reverse=True
)[:10],
"connected_components": nx.number_weakly_connected_components(G)
}
# PageRank (importance measure)
pagerank = nx.pagerank(G)
metrics["top_pagerank"] = sorted(
pagerank.items(), key=lambda x: x[1], reverse=True
)[:10]
return metrics
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.
- 2d ago First seen · 196 lines · 18 tokens per session scan A d63428cb1dd9
network-visualization-guide is a skill published in the GitHub repository wentorai/research-plugins (284 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,467 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…