What is setup-global?

A setup command that creates one shared skill graph for multiple projects instead of separate graphs for each project.

Use it when you explicitly want machine-wide graph data and a single build to serve all projects.

It lets every project see the same catalog, notes, ratings, and tags, while making clear that this shares information across otherwise unrelated repositories.

setup-global — Command for Claude Code by QuantumWars/project-graphx

Install

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.

Claude Code

/plugin marketplace add QuantumWars/project-graphx

Claude Code

/plugin install skill-graph

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/commands/quantumwars/project-graphx/setup-global/github.svg)](https://agentmods.dev/commands/quantumwars/project-graphx/setup-global)

Your own site

<a href="https://agentmods.dev/commands/quantumwars/project-graphx/setup-global"><img src="https://agentmods.dev/badge/commands/quantumwars/project-graphx/setup-global/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/commands/quantumwars/project-graphx/setup-global"><img src="https://agentmods.dev/badge/commands/quantumwars/project-graphx/setup-global.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan B 1 finding. 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.00018	$0.01463
Opus 5.5	$0.00007	$0.00585
Sonnet 5.5	$0.00004	$0.00293
Haiku 4.5	$0.00002	$0.00146

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

Security

Grade B, and why

setup-global scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

`~/.claude/settings.json`:

commands/setup-global.md · 133 lines

How it starts

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

Point every project at a single shared graph, so a skill catalogued once is visible everywhere and a note written in one project is readable from another.

Decide this first, out loud

The default is one graph per project, and that is the right default for most people: two projects never see each other's data, and nothing follows you between unrelated repos. Going global trades that away deliberately. Say so before changing anything, and get an explicit yes.

Going global means:

Every project on this machine reads and writes the same graph-data.json and overlay.json.
Per-project graphs already built are not deleted, but they stop being read. They are still on disk at <project>/.claude/graph/ and become live again if the setting is removed.
Notes, ratings and tags become machine-wide rather than belonging to one repo.
One build serves everything, so /skill-graph:build from any project rebuilds the shared graph.

If the user only wants "the same skills visible everywhere" and does not want shared notes, stop here and use /skill-graph:setup instead with absolute source roots — relative roots resolve against the project, absolute ones do not, so several projects can catalogue the same folders while keeping separate graphs. That needs no settings change and no restart.

1. Choose where the shared graph lives

Ask. Offer ~/.claude/graph as the default, and say plainly what it means: this is machine-wide state living in the home directory rather than travelling with any repository. If the user keeps agent data inside projects as a rule, this is the deliberate exception, and it is worth them saying yes to rather than discovering later.

Anywhere writable works — a Dropbox folder, a synced directory, a path already under backup.

2. Find every source on the machine

Sources here must be absolute paths, because this config is read from every project and a relative root would resolve somewhere different each time.

Search the user's code directories for **/.claude/agents, **/.claude/skills, and any agents/ or skills/ folder belonging to a plugin, pruning node_modules. Show what you found with counts and let the user cut the list before writing it — a machine-wide search finds vendored copies and abandoned experiments as readily as the real thing.

Read the full file on GitHub · 133 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 · 133 lines · 18 tokens per session scan B 0ae26ab55d92

Subscribe to this mod's changes

setup-global is a command published in the GitHub repository QuantumWars/project-graphx (1 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 1,463 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Building agents

setup-global next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
setup-globalQuantumWars/project-graphx	Command	1	2mo ago	MIT	B	18	Claude Code
checklistgithub/spec-kit	Command	149k	2d ago	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	149k	2d ago	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	149k	2d ago	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	149k	2d ago	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	149k	2d ago	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	149k	2d ago	MIT	A	14	Claude Code

setup-global