This repository is the BTrace plugin marketplace for Claude Code, Codex, and Pi.
Each plugin has one shared implementation under plugins/. Tool-specific manifests live beside
one another so the workflow instructions and supporting scripts are maintained once.
| Plugin | Purpose |
|---|---|
btrace-development |
Repository conventions and build guidance for BTrace development. |
btrace-observability |
A composable SRE skill suite for diagnosing Java applications with BTrace probes. |
jfr-analyzer |
Systematic profile analysis with optional BTrace live-probe correlation. |
jafar-perf |
Guided JVM performance analysis on the Jafar MCP server: playbooks for CPU, latency, GC and memory, and specialist subagents. |
perf-engineer |
Evidence-driven optimization investigations with JFR, BTrace, and JMH. |
.claude-plugin/marketplace.json Claude Code catalog
.agents/plugins/marketplace.json Codex catalog
package.json Pi package manifest
extensions/mcp-servers.ts Pi MCP server registration
plugins/<name>/skills/ shared Agent Skills content
plugins/<name>/.claude-plugin/ Claude Code manifest
plugins/<name>/.codex-plugin/ Codex manifest
/plugin marketplace add btraceio/agent-plugins
/plugin install btrace-observability@btraceio-agent-plugins
pi install git:github.com/btraceio/agent-plugins
The package registers the jafar and btrace MCP servers through an extension. They start with JBang, and
btrace also needs JDK 11 or later on the host that can attach to the target JVM.
Clone this repository and add the checkout as a team marketplace:
git clone https://github.com/btraceio/agent-plugins.git codex plugin marketplace add /path/to/agent-plugins
Then install btrace-observability from the BTrace Agent Plugins catalog. Codex consumes the
catalog at .agents/plugins/marketplace.json.
Keep portable workflow instructions and scripts in plugins/<name>/skills/. Add only the
minimum platform-specific metadata or integration configuration required by each host.
Operational guidance in skills is deliberately self-contained: copy the relevant BTrace knowledge into the skill instead of linking to BTrace source documentation. The validation gate keeps that copy in sync with the BTrace source checkout.
From a fresh clone, install the tracked pre-push hook once:
scripts/install-git-hooks.sh
The gate expects a BTrace checkout at ../btrace. Otherwise, set its location before validating or
pushing:
export BTRACE_SOURCE_DIR=/path/to/btrace
scripts/validate-marketplace.sh
git pushThe hook runs this validation automatically before every push. It validates the Claude marketplace,
JSON manifests, skill front matter, the absence of source-documentation URLs in skills, and selected
facts against the BTrace checkout. It also validates the provider-neutral observability eval corpus.
Update references/btrace-source-facts.txt together with any intentional change to embedded BTrace
operational guidance. See the eval guide to score captured model responses.
GitHub Actions runs the same repository checks on pushes and pull requests. See
CONTRIBUTING.md, SECURITY.md, and RELEASE.md
for contribution, security, and release policy.