What is using-the-graph?

A guide for using a skill graph: a map of installed skills, their relationships, and the projects that use them. It answers questions about what a skill does, what to install, and how skills are connected.

Use it to search for skills, inspect a skill's purpose, find related skills, see which projects use one, or review a project's installed skills.

It prevents choosing skills based only on filenames or assumptions. The graph can show which capabilities match a task and whether a project already uses them.

using-the-graph — Skill for Claude Code by QuantumWars/project-graphx

Install

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.

Any agent

npx skills add QuantumWars/project-graphx --skill using-the-graph

Clone the repo

git clone --depth 1 https://github.com/QuantumWars/project-graphx

Made for: Claude Code.

Or install skill-graph, the plugin that ships this one along with the rest of its 1 skill, 6 commands, 1 hook, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/quantumwars/project-graphx/using-the-graph/github.svg)](https://agentmods.dev/skills/quantumwars/project-graphx/using-the-graph)

Your own site

<a href="https://agentmods.dev/skills/quantumwars/project-graphx/using-the-graph"><img src="https://agentmods.dev/badge/skills/quantumwars/project-graphx/using-the-graph/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/quantumwars/project-graphx/using-the-graph"><img src="https://agentmods.dev/badge/skills/quantumwars/project-graphx/using-the-graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 899 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00062	$0.00899
Opus 5.5	$0.00025	$0.00360
Sonnet 5.5	$0.00012	$0.00180
Haiku 4.5	$0.00006	$0.00090

Measured 2mo ago against content hash 3cdac2add9fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

using-the-graph 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 2mo 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.

skills/using-the-graph/SKILL.md · 71 lines

How it starts

The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Using the skill graph

The skill-graph MCP server answers questions about the agents and skills catalogued for this project from data built by scanning real files. Prefer it to reading directories: a .claude/skills listing gives you names, and the graph gives you what each one is, what references it, and who already uses it.

First, is there a graph?

Every tool fails with the same message when the project has no graph yet: No graph found at <path>. That is a first-run state, not a fault. Tell the user to run /skill-graph:setup and then /skill-graph:build. Do not fall back to guessing from filenames without saying that is what you are doing.

Which tool answers which question

The question	The tool
"what should I install for X"	`search_ranked`, then `get_file_set` to narrow
"what is this skill"	`get_node`
"what is important here"	`best_skills`
"what else relates to this"	`graph_neighbors`, `related_by_connections`
"how are these two connected"	`graph_path`
"who already uses this"	`projects_using`
"what does this project have"	`project_installed_skills`
"what categories/tags exist"	`list_categories`, `list_tags`

find_skills is a fuzzy name/description match; search_ranked also weighs how connected and how used each hit is. Reach for search_ranked when the user described a need, and find_skills when they named a thing.

What the numbers mean, and do not mean

An edge exists because one file's text mentions another node's name — a real, counted occurrence, not a curated relationship. High degree means "widely mentioned", which is usually but not always "important": a skill named after a common word accumulates edges by coincidence. Say "referenced by N others" rather than "the most important", because the first is what was measured.

usedBy and usesCount come from a filesystem scan of the configured scan roots. Absent means "not found under those roots" — never "unused". If scanRoots is empty, every one of these numbers is zero and reporting them as usage would be wrong.

Read the full file on GitHub · 71 lines

Changes

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.

2mo ago First seen · 71 lines · 62 tokens per session scan A 3cdac2add9fa

Subscribe to this mod's changes

using-the-graph is a skill published in the GitHub repository QuantumWars/project-graphx (1 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 899 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-31.

Building agents

using-the-graph next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
using-the-graphQuantumWars/project-graphx	Skill	1	2mo ago	MIT	A	62	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	2d ago	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	2d ago	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	315k	5d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code