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 skills add xentivo/claude-plugins --skill graphgit clone --depth 1 https://github.com/xentivo/claude-pluginsWrote 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/xentivo/claude-plugins/graph)<a href="https://agentmods.dev/skills/xentivo/claude-plugins/graph"><img src="https://agentmods.dev/badge/skills/xentivo/claude-plugins/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.
<a href="https://agentmods.dev/skills/xentivo/claude-plugins/graph"><img src="https://agentmods.dev/badge/skills/xentivo/claude-plugins/graph.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.00000 | $0.00802 |
| Opus 5.5 | $0.00000 | $0.00321 |
| Sonnet 5.5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
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 1mo 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
Strukturalna mapa repo (graph.json)
Zamiast re-czytać dziesiątki plików, najpierw skonsultuj graph.json w
korzeniu projektu. Generator jest wbudowany w ten Skill — żadnych
zewnętrznych narzędzi (tylko biblioteka standardowa Pythona). Kod nigdy nie
opuszcza maszyny. Skill jest przenośny: dystrybuowany jako plugin
claude-memory, ta sama logika działa w każdym projekcie.
Odświeżenie mapy
Uruchom wbudowany generator z korzenia projektu. ${CLAUDE_SKILL_DIR}
wskazuje katalog tego Skilla niezależnie od miejsca instalacji (plugin,
projekt, globalnie) i bieżącego katalogu roboczego:
python3 "${CLAUDE_SKILL_DIR}/generate_graph.py"
Zapisuje graph.json w bieżącym katalogu (deterministycznie, posortowane —
czyste diffy). Odśwież zawsze, gdy:
- pliki zmieniły się od pola
generatedwgraph.json, - dodano/usunięto/przeniesiono pliki,
- zaczynasz nowe zadanie wymagające orientacji w strukturze.
Sprawdzenie aktualności: porównaj graph.json generated z
git log -1 --format=%cI — jeśli graf starszy niż ostatni commit lub są
niezacommitowane zmiany, wygeneruj ponownie.
Odpytywanie zamiast czytania
graph.json ma kształt:
stats— liczba węzłów/krawędzi/plików,nodes[]—{id, type, size, symbols?}(symbols= funkcje/klasy najwyższego poziomu w plikach.py),edges[]—{from, to, kind},kind∈link|wikilink|import.
Najpierw odczytaj/przefiltruj graph.json (Read albo grep), żeby ustalić:
które pliki są kluczowe, co z czym powiązane, gdzie żyje dany symbol — i
dopiero wtedy otwieraj konkretne pliki. To tnie zużycie tokenów względem
ślepego czytania repo.
Integracja z pamięcią
Przy /save (Skill save) odśwież graph.json, żeby mapa nie odstawała od
stanu repo. Opcjonalny git hook pre-commit może wołać generator
automatycznie — instaluj tylko na wyraźną prośbę użytkownika.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 55 lines · 0 tokens per session scan A 2161ac765aa1
graph is a skill published in the GitHub repository xentivo/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 802 tokens. 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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…