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 agentmods add skills/opentrace/opentrace/graphnpx 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.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 | $0.00195 | $0.00772 |
| Opus 5 | $0.00097 | $0.00386 |
| Sonnet 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 4d 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.
- 4d ago First seen · 66 lines · 195 tokens per session scan A c35e02e34fee
graph is a skill published in the GitHub repository opentrace/opentrace (106 stars, last pushed 22d ago), licensed Apache-2.0. It adds 195 tokens to every session and 772 once invoked, about $0.0010 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-30.
Other skills, from other repositories
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-benchmark
Golang benchmarking, profiling, and performance measurement. Use when writing, running, or comparing Go benchmarks, profiling hot paths with pprof, interpreting CPU/memory/trace profiles, analyzing results with benchstat, setting up CI benchmark regression detection, or investigating production performance with…
golang-dependency-injection
Comprehensive guide for dependency injection (DI) in Golang. Covers why DI matters (testability, loose coupling, separation of concerns, lifecycle management), manual constructor injection, and DI library comparison (google/wire, uber-go/dig, uber-go/fx, samber/do). Use this skill when designing service architecture…
golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports github.com/99designs/gqlgen or github.com/graph-gophers/graphql-go.
golang-naming
Go (Golang) naming conventions — covers packages, constructors, structs, interfaces, constants, enums, errors, booleans, receivers, getters/setters, functional options, acronyms, test functions, and subtest names. Use this skill when writing new Go code, reviewing or refactoring, choosing between naming alternatives…
golang-pkg-go-dev
Golang package and module lookup via godig, a pkg.go.dev API client (CLI + MCP server). Use for any Go/Golang library's documentation, API signatures, symbols, usage examples, which versions exist, licenses, whether a dependency has CVEs, or who imports a package — prefer this over Context7 for any Go package or…