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/phoenixWrote 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/rules/arize-ai/phoenix/client-migration)<a href="https://agentmods.dev/rules/arize-ai/phoenix/client-migration"><img src="https://agentmods.dev/badge/rules/arize-ai/phoenix/client-migration/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/rules/arize-ai/phoenix/client-migration"><img src="https://agentmods.dev/badge/rules/arize-ai/phoenix/client-migration.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.00000 | $0.04160 |
| Opus 5.5 | $0.00000 | $0.01664 |
| Sonnet 5.5 | $0.00000 | $0.00832 |
| Haiku 4.5 | $0.00000 | $0.00416 |
Grade A, and why
client-migration 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 565 lines · 0 tokens per session scan A b56cadf179dd
client-migration is a cursor rule published in the GitHub repository Arize-ai/phoenix (11,859 stars, last pushed today), with no licence file. It costs nothing until one of its globs matches a file; then it loads 4,160 tokens. 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-30.
Other cursor rules, from other repositories
js-sdk-genai-instrumentation
Guide for aligning JS SDK GenAI provider instrumentations with OTel semantic conventions and the Python SDK reference implementation.
js-sdk-genai-framework-instrumentation
Guide for implementing JS SDK agent and framework instrumentations, such as LangChain, LangGraph, OpenAI Agents, Claude Agent SDK, Google ADK, and Vercel AI.
coding-agents-hook
Authoring and testing coding-agent hook adapters, including payload probing, session state, capture modes, and plugin manifests. Consult the telemetry convention when changing canonical attributes.
coding-agents-convention
Canonical coding-agent telemetry schema, inbound mappings, and data contracts. Applies to semantic conventions, emission, processing, and readers—not hook implementation mechanics.
controller-design
Design principles and invariants for the OpenLIT controller (Go agent that discovers and instruments LLM workloads) and the Agents-page server layer that consumes its data.
frontend
UI, messaging, project hierarchy, and CE/enterprise-boundary guidance for OpenLIT client presentation code.