OpenInference is a set of conventions and instrumentation plugins for tracing AI applications with OpenTelemetry. It helps developers record language-model calls, retrieval from vector stores, and external tool use for analysis in compatible observability backends. The catalogue entries support instrumentation and use of these tracing conventions.
Borrowing it
Nothing to install: this file belongs to Arize-ai/openinference. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Arize-ai/openinference/main/.agents/skills/issue-triage/SKILL.mdgit clone --depth 1 https://github.com/Arize-ai/openinferenceWrote 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/arize-ai/openinference/issue-triage)<a href="https://agentmods.dev/skills/arize-ai/openinference/issue-triage"><img src="https://agentmods.dev/badge/skills/arize-ai/openinference/issue-triage/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/arize-ai/openinference/issue-triage"><img src="https://agentmods.dev/badge/skills/arize-ai/openinference/issue-triage.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00119 | $0.08817 |
| Opus 5.5 | $0.00048 | $0.03527 |
| Sonnet 5.5 | $0.00024 | $0.01763 |
| Haiku 4.5 | $0.00012 | $0.00882 |
Grade A, and why
issue-triage 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.
How it starts
The opening of the file, as written. The whole thing — 654 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Triage
Triage open Arize-ai/openinference issues so each one is ready to work on
immediately: correctly typed, sufficiently specified, labelled by language,
package and component, checked against the requirements every instrumentor must
meet, sized, and readable.
Work the stages in order, per issue. Stages 1–7 are general triage for this
repo. Stage 8 applies a gate policy from references/ — the
audience-specific question of who should pick the issue up — and is the only
stage that knows about a policy.
| Stage | Question | Writes |
|---|---|---|
| 1 | Bug, enhancement, or something else? Is the title informative? | bug/enhancement/documentation/cleanup/question, title |
| 2 | Is there enough information to start? | needs information, gate labels |
| 3 | Which language, package and component? | language: *, instrumentation: *, new instrumentation, c/* |
| 4 | Which mandatory instrumentor requirements does it touch, and does it spell them out? | c/trace-config, c/context-attributes, c/suppress-tracing, c/semcov, triage block |
| 5 | How complex is it? | size:S/size:M/size:L |
| 6 | Does a complex issue need investigation or repro? | comment |
| 7 | Is it readable? | body |
| 8 | Does it qualify for a gate policy? | gate labels |
Between stages 5 and 6, check whether the issue already shipped — see Already shipped?. It is the cheapest high-value thing triage does, and it changes both the size and the gate.
Never close an issue, never touch a pull request, never run git, never run the test suites.
What is different about this repo
OpenInference is a multi-language instrumentation monorepo, not an application. That shapes every stage:
- Three languages (
python/,js/,java/) each ship a core library, a semantic-conventions package and a set of instrumentors. The same library is often instrumented in two languages (OpenAI, Anthropic, LangChain, Bedrock, Google GenAI, MCP, BeeAI, Claude Agent SDK, OpenAI Agents, Google ADK). An issue is rarely "about OpenAI"; it is about the Python OpenAI instrumentor. - Every instrumentor has five mandatory requirements (
CLAUDE.md→ Requirements): support suppressing tracing, propagate context attributes (session ID, user ID, metadata, tags, prompt template), respectTraceConfigfor masking sensitive data, follow the OpenInference semantic conventions, and include comprehensive tests. Stage 4 exists to check issues against these. - Fixes often need a recorded cassette against a paid provider API. That is a real barrier for newcomers and an absolute one for autonomous agents, and the gate policies read it.
- The
triagelabel feeds a Slack digest..github/workflows/collect-customer-issues.yamlposts every open issue carryingtriageto maintainers each weekday so a human responds. Automated labelling is not a response, so this skill leavestriagein place by default — see Finishing an issue. - Two labels trigger GitHub Actions.
good-agent-issuestartsclaude-implement-issue.yml, which assigns the issue, marks itagent-in-progressand opens a PR;agent-fixstarts a support-agent fix pipeline. Neither is ever applied outside an explicitly enabled gate policy. (When this skill runs under the scheduled workflow it writes withGITHUB_TOKEN, whose events do not start other workflows — agood-agent-issueit applies waits for a maintainer to re-apply it. Report every one you apply so that hand-off happens.) - An issue carrying
agent-in-progressis read-only. An agent is working it and reading its labels and body. No stage writes to it — no labels, no title, no body, no comment. Judge it, and report what you would have done.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 654 lines · 119 tokens per session scan A 1d31ae3c732a
issue-triage is a skill published in the GitHub repository Arize-ai/openinference (1,291 stars, last pushed today), licensed Apache-2.0. It adds 119 tokens to every session and 8,817 once invoked, about $0.0005 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-09-18.
Other skills, from other repositories
trulens-instrumentation
Instrument LLM apps with TruLens OTEL-based tracing - from setup to debugging and optimization.
frontmcp-observability
Use when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server. Covers zero-config OpenTelemetry distributed tracing across all flows; the this.telemetry API for custom spans, events, and attributes in tools, plugins, agents, and skills; structured JSON logging with trace correlation and…
observability-phoenix
Open-source AI observability platform for LLM tracing, evaluation, and monitoring. Use when debugging LLM applications with detailed traces, running evaluations on datasets, or monitoring production AI systems with real-time insights.
iterate-prd
Only use when the user explicitly invokes this skill by name.
create-design-discussion
Only use when the user explicitly invokes this skill by name.
iterate-structure-outline
Only use when the user explicitly invokes this skill by name.