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 opentrace/opentrace --skill graphgit clone --depth 1 https://github.com/opentrace/opentraceWrote 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/opentrace/opentrace/graph)<a href="https://agentmods.dev/skills/opentrace/opentrace/graph"><img src="https://agentmods.dev/badge/skills/opentrace/opentrace/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/opentrace/opentrace/graph"><img src="https://agentmods.dev/badge/skills/opentrace/opentrace/graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00195 | $0.00772 |
| Opus 5.5 | $0.00078 | $0.00309 |
| Sonnet 5.5 | $0.00039 | $0.00154 |
| Haiku 4.5 | $0.00019 | $0.00077 |
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
The user wants to build, refresh, or explore the OpenTrace knowledge graph. This skill is the on-ramp — point at the right slash command and run it.
Request
$ARGUMENTS
Routing
Match the user's intent to one of the commands below. When in doubt, default to
/build for build / refresh and /interrogate for question-answering.
| Intent | Command |
|---|---|
| Build the graph from scratch on a folder or GitHub URL | /build [path or url] |
| Index only (no clustering / analysis) | /index [path] |
| Re-run clustering | /cluster |
| Surface god nodes, bridges, suggested questions | /analyze |
| Quick exploration of a named component | /explore <name> |
| Read-only Q&A over the graph | /interrogate "<question>" |
| Shortest path between two graph nodes | /path <A> <B> |
| Obsidian vault export | /export-obsidian |
| Browsable markdown report | /export-report |
| GraphML for Gephi / yEd | /export-graphml |
| Counts of indexed nodes by type | /graph-status |
If the user asked a question the graph could answer directly (e.g. "what's
connected to AuthMiddleware?") and .opentrace/index.db exists, run
/interrogate yourself rather than asking the user which command to use.
When the graph does not exist yet
If .opentrace/index.db is missing and the user is asking a graph-flavoured
question, offer to run /build first, then answer against the freshly built
graph.
Conventions
- Only
CALLSedges carry aconfidencevalue — a float from the call resolver (1.0 for an exact in-scope match, lower for cross-file and heuristic ones). No other edge type has one, so don't report a confidence for edges that don't carry it. - After any build, the OpenTrace MCP tools (
search_graph,get_node,traverse_graph,list_nodes,get_stats) read the same.opentrace/index.dbthe slash commands wrote to. There is one graph, not two.
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 · 66 lines · 195 tokens per session scan A c35e02e34fee
graph is a skill published in the GitHub repository opentrace/opentrace (108 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 195 tokens to every session and 772 once invoked, about $0.0008 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 skills, from other repositories
llm-runtime
Integrate, stream, and orchestrate frontier LLM APIs with robust structured outputs, tool call schemas, prompt caching, and resilient backoff handling. Use when implementing AI agent runtimes, tool-calling loops, streaming SSE endpoints, or optimizing token usage and model latency.
knowledge-model-and-provider-runtime-provider-resilience-admission-and-observability
A codebase guide for handling unreliable AI provider requests across agents and sessions, including retries, circuit breakers, fair queues, stalled streams, cache tracking, and health checks.
knowledge-model-and-provider-runtime
A codebase guide for choosing AI models and providers, sending requests, recovering from failures, and recording runtime information.
knowledge-model-and-provider-runtime-model-catalog-configuration-and-credentials
A codebase guide for defining AI models and providers, selecting endpoints and credentials, configuring fallback channels, and migrating model identifiers.
code_interpreter
A tool for running Python code in an isolated environment. Python is a programming language often used for calculations, data processing, file-format conversion, and preparing chart data.
ds-notebook-strict-code
Use only when the user explicitly requests strict code-cell-only output for a Jupyter or undergraduate data-science task, or when an ITX2007 assignment requires that format. Do not activate for ordinary data analysis or explanation requests.