A code-tracing tool that follows a feature across files, programming languages, and services. It can also find the path between two named pieces of code.

Use it to follow a feature from a user interface call to a backend route, handler, and data, or to explain how two code locations are linked.

It removes the need to manually search both the frontend and backend and guess how they are connected.

glia-trace — Skill for Claude Code by James-Chahwan/repo-graph

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 James-Chahwan/repo-graph --skill glia-trace

Clone the repo

git clone --depth 1 https://github.com/James-Chahwan/repo-graph

Made for: Claude Code.

Or install repo-graph, the plugin that ships this one along with the rest of its 8 skills.

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/james-chahwan/repo-graph/glia-trace/github.svg)](https://agentmods.dev/skills/james-chahwan/repo-graph/glia-trace)

Your own site

<a href="https://agentmods.dev/skills/james-chahwan/repo-graph/glia-trace"><img src="https://agentmods.dev/badge/skills/james-chahwan/repo-graph/glia-trace/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/james-chahwan/repo-graph/glia-trace"><img src="https://agentmods.dev/badge/skills/james-chahwan/repo-graph/glia-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 806 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.00065	$0.00806
Opus 5.5	$0.00026	$0.00322
Sonnet 5.5	$0.00013	$0.00161
Haiku 4.5	$0.00006	$0.00081

Measured 5d ago against content hash 4d93a431b413, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

glia-trace 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.

claude-plugin/skills/glia-trace/SKILL.md · 31 lines

How it starts

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

Trace a feature across the stack

Connect code across modules and across the front/back boundary in one call, instead of grepping both sides and guessing the link.

Transports

Use whichever is available, in this order: the repo-graph MCP tools when loaded (mcp__repo-graph__<tool>, or mcp__plugin_repo-graph_repo-graph__<tool> from the Claude Code plugin; they may be deferred, so search your tool list first); the glia CLI when on PATH; else uvx --from glia-cli glia <command> .. (no install; the first run downloads the wheel); else uvx mcp-repo-graph <verb>. The MCP tools and uvx mcp-repo-graph print the same text; the glia CLI answers the same question with --json rows (file, line, tier). Run any of them at the repo root (. below).

Want	MCP tool call	glia CLI	uvx mcp-repo-graph
A feature end to end	`trace from_node=<feature>`	`glia trace . <feature> --json`	`uvx mcp-repo-graph trace "<feature>"`
The path from A to B	`trace from_node=<a> to_node=<b>`	`glia trace . <a> --to <b> --json`	`uvx mcp-repo-graph trace "<a>" "<b>"`
Why A and B are joined, edge by edge		`glia why . <a> <b> --json`
Every entry point and where it goes	`orient`	`glia flows . --json`	`uvx mcp-repo-graph orient`

Steps

One argument traces a feature: a keyword, a route (GET /api/users) or an entry point from glia flows . --json. You get ranked distinct paths from the entry through the stack, each hop labelled with its mechanism (CALLS, HTTP_CALLS, HANDLED_BY, queue, event, data access), with cross-service hops counted. --depth (default 6) caps the hops and --max-paths (default 10) the paths: glia trace . checkout --depth 8 --json.
Two names give the paths between them: glia trace . <a> --to <b> --json. Not sure of the names? glia find . <word> --json first and use the qnames.
To see why one hop exists, glia why . <a> <b> --json prints the edge's evidence: its tier, the rule that made it and the site (file, line) it was read at.
Report the path file by file, with file:line for each hop.

Read the full file on GitHub · 31 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.

5d ago First seen · 31 lines · 65 tokens per session scan A 4d93a431b413

Subscribe to this mod's changes

glia-trace is a skill published in the GitHub repository James-Chahwan/repo-graph (55 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 806 once invoked, about $0.0003 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-11-02.

Debugging

glia-trace next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
glia-traceJames-Chahwan/repo-graph	Skill	55	3d ago	MIT	A	65	Claude Code
systematic-debuggingopen-metadata/OpenMetadata	Skill	16k	yesterday	Apache-2.0	A	37	Claude Code
log-error-digestzebbern/claude-code-guide	Skill	4.7k	3d ago	MIT	A	71	Claude Code, Codex
cwv-optimizeradobe/skills	Skill	319	yesterday	Apache-2.0	A	112	Claude Code
ci-fixersipyourdrink-ltd/bernstein	Skill	1.2k	yesterday	Apache-2.0	A	15	Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skills	Skill	1.9k	23d ago	MIT	A	36	Claude Code
triaging-web-analytics-supportPostHog/posthog	Skill	41k	yesterday	none	A	151	Claude Code, Codex