Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add vipzhengmingming/oh-my-powers/plugin install create-llm-wikiWrote 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/vipzhengmingming/oh-my-powers/graph-wiki)<a href="https://agentmods.dev/skills/vipzhengmingming/oh-my-powers/graph-wiki"><img src="https://agentmods.dev/badge/skills/vipzhengmingming/oh-my-powers/graph-wiki/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/vipzhengmingming/oh-my-powers/graph-wiki"><img src="https://agentmods.dev/badge/skills/vipzhengmingming/oh-my-powers/graph-wiki.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.00059 | $0.00462 |
| Opus 5 | $0.00030 | $0.00231 |
| Sonnet 5 | $0.00012 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
graph-wiki 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 9d 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.
What it actually says
Graph Wiki
Generate a visual relationship graph from the project's LLM wiki.
Reference: references/llm-wiki.md for wiki architecture conventions.
Agent: the wiki-grapher agent handles the actual analysis and generation — this skill coordinates the flow.
Steps
-
Read
references/llm-wiki.mdto understand wiki conventions. -
Check that the wiki exists (
./llm-wiki/index.md). If not, suggest the user run/create-llm-wiki:init-wikifirst. -
Scan
./llm-wiki/pages/*.mdfor content and[[wikilinks]]. Build a graph data structure:- Nodes: each wiki page →
{ id, label, summary, group } - Edges: each
[[wikilink]]→{ source, target, label }. Also infer implicit relationships from shared keywords.
- Nodes: each wiki page →
-
Ask user for output format (or use the argument if provided):
html— Generate interactive D3.js graph. Pipe JSON to${CLAUDE_PLUGIN_ROOT}/scripts/graph-viz.js, write output to./llm-wiki/graph.html. Tell user to open it in a browser.obsidian— Add/update[[wikilinks]]in page files. Tell user to open Obsidian and use Graph View.
-
Execute based on user's choice.
-
Confirm where the output was generated and how to view it.
Important Notes
- Check existing
[[wikilinks]]first — don't duplicate. - For implicit relationships, add a
labelexplaining the connection. ${CLAUDE_PLUGIN_ROOT}expands to the plugin root in shell commands — pass it as-is.- The graph-viz.js script reads JSON from stdin and writes HTML to stdout.
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.
- 9d ago First seen · 41 lines · 59 tokens per session scan A 11ebf7461757
graph-wiki is a skill published in the GitHub repository vipzhengmingming/oh-my-powers (5 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 462 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…