Borrowing it
Nothing to install: this file belongs to cognitx-leyton/codegraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cognitx-leyton/codegraph/main/.claude/commands/trace-endpoint.mdgit clone --depth 1 https://github.com/cognitx-leyton/codegraphWrote 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/commands/cognitx-leyton/codegraph/trace-endpoint)<a href="https://agentmods.dev/commands/cognitx-leyton/codegraph/trace-endpoint"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/trace-endpoint/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/commands/cognitx-leyton/codegraph/trace-endpoint"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/trace-endpoint.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.00014 | $0.00691 |
| Opus 5.5 | $0.00006 | $0.00276 |
| Sonnet 5.5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
trace-endpoint 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage
/trace-endpoint <url_substring>
Matches against :Endpoint.path CONTAINS $ARGUMENTS — so partial matches work (/users picks up /users/:id, /users/profile, etc.).
Runs two queries in sequence:
- Surface — the matched endpoints and their handler methods (the API shape).
- Reach — every method reachable within 4
CALLShops from each handler, grouped by enclosing class (the data-and-compute reach).
Useful for impact analysis ("what breaks if I change this URL?"), security review ("what does this public endpoint touch?"), and onboarding ("show me a feature end-to-end").
What this does
codegraph query "
MATCH (m:Method)-[:HANDLES]->(e:Endpoint)
WHERE e.path CONTAINS '$ARGUMENTS'
OPTIONAL MATCH (ctrl:Class)-[:HAS_METHOD]->(m)
RETURN 'surface' AS layer,
e.method AS http_method,
e.path AS route,
ctrl.name AS controller,
m.name AS handler,
e.file AS file
ORDER BY e.path
LIMIT 20
"
codegraph query "
MATCH (m:Method)-[:HANDLES]->(e:Endpoint)
WHERE e.path CONTAINS '$ARGUMENTS'
MATCH path = (m)-[:CALLS*1..4]->(target:Method)
MATCH (enclosing:Class)-[:HAS_METHOD]->(target)
WITH DISTINCT enclosing.name AS class, target.name AS method, target.file AS file
RETURN 'reach' AS layer, class, method, file
ORDER BY class, method
LIMIT 100
"
Caveats
- Python has no
:Endpointnodes yet. Stage 1 Python only captures classes / functions / imports / decorators; FastAPI / Flask / Django route detection lands in Stage 2. Running this against a URL from a Python-only project returns zero rows. Document the gap rather than pretending the graph has coverage it doesn't. - Only typed CALLS resolve reliably. Python's name-resolved calls (
obj.foo()whereobj's type isn't known) may miss. TS:this.x()resolves; dynamic dispatch may not. - 4-hop bound is a trade-off. Deep call chains (e.g. orchestrator → saga → worker → DB) may exceed it. Raise to
*1..6if you're doing deep security review — slower but more complete. CALLS_ENDPOINTis the inverse — that's the edge for outgoing HTTP calls to an endpoint (e.g. frontend fetching from backend). If you want "who hits this endpoint from elsewhere", queryCALLS_ENDPOINTinstead.
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 · 60 lines · 14 tokens per session scan A ab4c9375ef8c
trace-endpoint is a command published in the GitHub repository cognitx-leyton/codegraph (12 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 691 once invoked, about $0.0001 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-30.
Other commands, from other repositories
grasp-build-graph
Run graspanalyze + graspminimalcontext for the current repo, store the sessionid, and report a 100-token orientation.
cloudflare-durable-objects:optimize
Interactive Durable Objects performance optimization assistant. Analyzes existing DO code and provides specific optimization recommendations with implementation guidance.
doctor
Diagnose the PyWry install (Python interpreter, pywry[mcp] extra, native binary, MCP server reachability).
va
A read-only security review of a codebase across eight architecture areas, with findings checked against file-and-line evidence.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
compliance
A follow-up security check that verifies whether earlier findings were fixed and, depending on the selected mode, looks for new problems.