A Claude Code plugin that records coding sessions as traces, which are structured records of what happened. It captures sessions, conversation turns, tool calls, and model responses in Orq.

It is for sending Claude Code session activity to Orq and reviewing the sequence of prompts, tool use, and model responses.

It provides a record of how a coding session progressed, so activity can be inspected after the fact instead of relying on memory or terminal output.

orq-trace — Plugin by orq-ai

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.

Claude Code

/plugin marketplace add orq-ai/assistant-plugins

agentmods

npx agentmods add plugins/orq-ai/assistant-plugins/trace-hooks

Clone the repo

git clone --depth 1 https://github.com/orq-ai/assistant-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

orq-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 yesterday.

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.

plugins/trace-hooks/.claude-plugin/plugin.json · 154 lines

How it starts

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

{
  "name": "orq-trace",
  "description": "Automatically trace Claude Code sessions to Orq. Captures sessions, turns, tool calls, and LLM responses as hierarchical OTLP spans.",
  "version": "0.4.0",
  "author": {
    "name": "Orq AI"
  },
  "license": "MIT",
  "keywords": ["orq", "claude-code", "otel", "otlp", "tracing"],
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.js",
            "async": true,
            "silent": true,
            "timeout": 30
          }
        ]
      }
    ],
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/user-prompt-submit.js",
            "async": true,
            "silent": true,
            "timeout": 30
          }
        ]
      }
    ],
    "PostToolUse": [
      {
        "matcher": "*",
        "hooks": [
          {
            "type": "command",
            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/post-tool-use.js",
            "async": true,
            "silent": true,
            "timeout": 30
          }
        ]
      }
    ],
    "PostToolUseFailure": [
      {
        "matcher": "*",
        "hooks": [
          {
            "type": "command",
            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/post-tool-use-failure.js",
            "async": true,
            "silent": true,
            "timeout": 30
          }
        ]
      }
    ],
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/stop.js",
            "async": false,
            "silent": true,
            "timeout": 30
          }
        ]
      }
    ],
    "StopFailure": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "node ${CLAUDE_PLUGIN_ROOT}/hooks/stop-failure.js",

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

yesterday First seen · 154 lines scan A f1a7b2b97a64

Subscribe to this mod's changes

orq-trace is a plugin published in the GitHub repository orq-ai/assistant-plugins (6 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.

Data and AI

orq-trace

Getting it into your agent

Grade A, and why

Nothing flagged

How it starts

What this file has done since we first saw it

Other plugins, from other repositories

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc

ecc