oxagen

Oxagen — Claude Code plugin

Ontology layer for AI agents. Typed, queryable knowledge graph exposed to Claude Code as MCP-native tools so every answer, edit, triage, or recall is grounded in deterministic graph context instead of guessing.

• Docs: https://docs.oxagen.ai/plugins/claude-code-plugin
• App: https://app.oxagen.ai
• Issues: https://github.com/oxagenai/claude-code-plugin/issues
• Marketplace listing: oxagenai/claude-code-plugin

---

TL;DR

Install once. Get:

• A typed, deterministic knowledge graph of your workspace (code, history, tests, CI, security alerts, incidents, ownership, runbooks, customers — whatever the workspace ontology tracks).
• Always-on memory — every meaningful action is captured, recurring patterns are detected, past failures are injected as warnings before similar work, and procedures get promoted to reusable recipes.
• 50+ slash commands under /oxagen:* covering discovery, traversal, history, tests, CI, security, memory, incidents, and multi-agent coordination.
• A SessionStart hook that pins three guarantees on every turn: graph first, memory always recalled, coordination respected. Persists across /clear and /compact.

---

Install

From the Claude Code plugin marketplace (recommended)

# Add the Oxagen marketplace
/plugin marketplace add oxagenai/claude-code-plugin

# Install the plugin
/plugin install oxagen@oxagen

That's it — no manual symlinks, no ~/.claude/plugins editing. The manifest, MCP server config, hooks, commands, and skills all come from the marketplace tree.

Local development install

If you've cloned this repo and want to dogfood your changes:

ln -s "$(pwd)" ~/.claude/plugins/oxagen

Then restart Claude Code.

Wire your workspace

/oxagen:setup

The command opens https://app.oxagen.ai/setup/claude-code in your browser, walks you through workspace + GitHub repo selection, hands back a one-line install string, writes ~/.claude/oxagen.local.json, polls until the first ingest is ready, and verifies the MCP tool list is live.

Add to your shell profile so the MCP token survives restarts:

export OXAGEN_MCP_TOKEN="$(jq -r .token ~/.claude/oxagen.local.json)"

Verify with:

/mcp

You should see oxagen listed with its full tool set.

---

What the plugin guarantees

When the Oxagen plugin is enabled, on every session the SessionStart hook injects an <EXTREMELY_IMPORTANT> preamble that tells the agent:

1. Graph first, guess second. Before any non-trivial action — code edit, research synthesis, incident triage, ops change, customer-impact analysis, policy lookup — query the Oxagen graph (ontology.*, code.*, incident.*, security.*).
2. Memory always recalled. At the start of any task, call memory.recall (or memory.context_inject) on the intent. If a procedure or episode matches, prefer it over rediscovery. After meaningful work, persist what you learned.
3. Coordinate. Use agent.list_active_claims and agent.claim_work when other sessions may be touching the same scope.

The full routing policy lives in the oxagen:using-oxagen skill, which is loaded into the system prompt by the hook on startup, clear, and compact. The complete tool catalog and write-back conventions live in the oxagen:oxagen-tool-reference and oxagen:dogfooding skills, which are loaded on demand.

---

Real-world use cases — beyond agentic coding

The plugin's value is the typed graph + memory layer. Coding is the most obvious surface. It is not the only one. Anything Oxagen ingests becomes queryable and groundable.

Engineering

• Refactor with confidence. /oxagen:impact <symbol> returns callers, dependents, PageRank, and reach paths before you ship a signature change. Stops the "I didn't realize ten things called this" class of regression.
• Onboarding. /oxagen:repo-overview, /oxagen:module-tree, /oxagen:who-knows <symbol>, /oxagen:expert <login> — the new hire gets a cartography of the system and its owners in five minutes instead of three weeks.
• Dead-code audit. /oxagen:ask "list nodes with zero callers and no EXPORTS edge" returns provably dead symbols. Safe to delete.
• Architecture review. /oxagen:ask "show cycles in the call graph scoped to packages/oxagen" surfaces SCCs you can't see from grep.

Incident response & SRE