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/skyllwt/autosci/visualizenpx skills add skyllwt/AutoSci --skill visualizegit clone --depth 1 https://github.com/skyllwt/AutoSciWhat 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.00039 | $0.02966 |
| Opus 5 | $0.00019 | $0.01483 |
| Sonnet 5 | $0.00008 | $0.00593 |
| Haiku 4.5 | $0.00004 | $0.00297 |
Grade A, and why
visualize 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/visualize
Generate visualization artifacts for the OmegaWiki knowledge graph. Produces Obsidian graph config (color groups by entity type) and curated Canvas views with labeled typed edges. For interactive web exploration use the SPA Graph view (
tools/serve.py, then#/graph).
Inputs
--obsidian(optional): Generate/update.obsidian/graph.jsonwith entity-type color groups--canvas(optional): Generate Obsidian Canvas (.canvas) from graph data with labeled edges--focus <node_id>(optional): Center canvas on a specific node (e.g.,methods/my-method)--depth N(optional): BFS depth for focused canvas (default: 2)--types <list>(optional): Filter nodes to these page types, comma-separated (e.g.,papers,concepts)--edge-types <list>(optional): Filter edges to these semantic types, comma-separated (e.g.,builds_on,challenges)--all(optional, default if no flags): Generate all visualization artifacts
Outputs
wiki/.obsidian/graph.json— Obsidian graph color configuration (per-entity-type color groups)wiki/.obsidian/app.json— Obsidian app settings (only if not exists)wiki/canvases/knowledge-map.canvas— Full knowledge map Canvas with labeled edgeswiki/canvases/idea-evidence.canvas— Idea-centric subgraph Canvaswiki/canvases/focus-{node-id}.canvas— Focused Canvas (when --focus is used)- Console output: Obsidian plugin recommendations and setup instructions
The standalone-HTML explorer (wiki/graph-view.html) was retired; the
SPA Graph view at app/modules/graph.js (served by tools/serve.py)
covers the same use case and lives in the same codebase as the rest of
the frontend.
Wiki Interaction
Reads
wiki/graph/edges.jsonl— typed semantic edgeswiki/graph/citations.jsonl— bibliographic paper citationswiki/*/— all entity directories for page metadata (frontmatter)config/visualize.json— color palette and visualization preferences
Writes
wiki/.obsidian/graph.json— CREATE/OVERWRITE (local-only artifact, gitignored; regenerated each run fromconfig/visualize.json)wiki/.obsidian/app.json— CREATE only (never overwrite user customizations; gitignored)wiki/canvases/*.canvas— CREATE/OVERWRITE (local-only artifact, gitignored)
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 · 269 lines · 0 tokens per session scan A 69f3b346de6c
visualize is a skill published in the GitHub repository skyllwt/AutoSci (1,659 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 2,966 once invoked, about $0.0002 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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.