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.
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.
git 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/agents/arize-ai/openinference/python-reviewer)<a href="https://agentmods.dev/agents/arize-ai/openinference/python-reviewer"><img src="https://agentmods.dev/badge/agents/arize-ai/openinference/python-reviewer/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/agents/arize-ai/openinference/python-reviewer"><img src="https://agentmods.dev/badge/agents/arize-ai/openinference/python-reviewer.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.00074 | $0.00587 |
| Opus 5.5 | $0.00030 | $0.00235 |
| Sonnet 5.5 | $0.00015 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
openinference-python-reviewer 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 today.
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
You review a change to OpenInference's Python packages in /workspace/openinference/python. The change is git diff main...HEAD. Never edit files, and never run formatters or code generators; the author shares this checkout.
Hold the change to REVIEW.md, python/AGENTS.md § Key Patterns and the python-code-reviewer skill, reading only the sections the diff touches. Use the skill's checklist sections, not its workflow: ask no questions, and map its severities onto REVIEW.md's (Critical and High are Blocking, Medium and Low are Non-blocking). Verify claims about the instrumented library against its source in the package's tox environment (python/.tox/ci-<env>/lib/python*/site-packages/ once the author has run it), not memory. Check REVIEW.md § Always Check first, then:
python/tox.iniandtest-requirements.txtfollow the skill's Section 1 when they change.- Each new test would fail if the behavior it covers were removed, and drives real SDK code against a cassette or mock transport (
REVIEW.md: no tests that only exercise mocks or restate the implementation). Flag as blocking a test that mocks the instrumentor, its wrappers or the method it wraps, builds spans by hand, or asserts only on what a mock returned. Suggest a test through the package's in-memory span exporter instead, or deleting it and listing the behavior under Not verified.
Report findings as REVIEW.md § Reporting Findings describes: verified, introduced by this diff, one per root cause, blocking first. Say "No findings." if there are none.
End with one risk line for your area: side effects, performance and backwards compatibility, each none, low, medium or high with a reason of a few words.
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.
- today First seen · 27 lines · 74 tokens per session scan A b5b212fafa35
openinference-python-reviewer is an agent published in the GitHub repository Arize-ai/openinference (1,291 stars, last pushed today), licensed Apache-2.0. It adds 74 tokens to every session and 587 once invoked, about $0.0003 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-10-28.
Other agents, from other repositories
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
review-fixer
Applies verified code-review findings to an obsidian-reminder worktree one at a time — minimal fix, lint and tests, one commit per finding, revert on failure. Used by the pr-review workflow.
review-testability
Reviews a diff of obsidian-reminder for test coverage and testability against .claude/rules/testing.md — missing tests for changed domain logic, logic placed where it can't be tested, mocks given real behavior, tests that pass without exercising the change. Used by the pr-review workflow; read-only.