Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/tolgakisaogullari/sumelaos/graphify-code-graph)<a href="https://agentmods.dev/skills/tolgakisaogullari/sumelaos/graphify-code-graph"><img src="https://agentmods.dev/badge/skills/tolgakisaogullari/sumelaos/graphify-code-graph.svg" alt="Measured on agentmods" 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.00045 | $0.00697 |
| Opus 5 | $0.00023 | $0.00349 |
| Sonnet 5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
graphify-code-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 5d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tier-2: Graphify Code Graph
⚠️ Installation (Correct Info — Do Not Use npm)
The correct installation is uv tool install graphifyy (PyPI: graphifyy, double-y).
DO NOT use npm install -g @anthropic/graphify (outdated) or pip install graphify-code-graph (non-existent).
Important: No API Key Required for Queries
All query operations (query-graph.py, graphify query, graphify path, graphify explain) read from the local graphify-out/graph.json file. They are purely local — no network calls, no API keys, no cost. API keys are only needed for initial graph BUILD from docs/PDFs/images (not for querying an existing graph).
Routing
- Trigger: Query contains "where is X used", "who calls X", "what does X call", "if I change X what breaks" (or the equivalent in any language), or references function/class/method + asks about callers/callees/dependencies.
- Primary tool:
python .sumela/memory-plugins/graphify-code-graph/scripts/query-graph.py "<symbol>"--depth 2for transitive (2-hop)--impactfor incoming closure (what breaks if you change X)--relation callsto restrict to call edges--jsonfor machine-readable output
- Secondary tools:
graphify query "<symbol>" --budget 2000— BFS neighborhood walkgraphify explain "<symbol>"— plain-language node summarygraphify path "<src>" "<tgt>"— shortest path between nodes
- Fallback: If graphify not installed or graph.json missing → skip, fall through to Tier-4 (grep)
Graph Maintenance
- After code commits, run:
python scripts/auto-update-memory.py - This script is a cross-plugin orchestrator: updates Graphify graph, syncs to wiki, and checks Qdrant health
- Conditional: only run when code changed, not for pure handoff/summary sessions
Prerequisites
- Python 3.10+
- uv (recommended) or pipx:
uv tool install graphifyy pip install -r .sumela/memory-plugins/graphify-code-graph/requirements.txt- Run
/graphify .in IDE orgraphify update .in terminal (AST-only, no API key) to seedgraphify-out/graph.json - Optional:
graphify hook installfor auto-rebuild on commit
What ships with it
4 files 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.
- 5d ago First seen · 47 lines · 45 tokens per session scan A 39ba66c3c1a5
graphify-code-graph is a skill published in the GitHub repository tolgakisaogullari/SumelaOS (4 stars, last pushed 11d ago), licensed MIT. It adds 45 tokens to every session and 697 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…