phoenix-cli-development

A development guide for Phoenix CLI, a command-line tool whose commands follow a noun-then-verb structure.

In plain words
What is it for?
Use it when adding or changing CLI commands, handling configuration, choosing output formats, or setting exit codes.
Why use it?
It explains how commands should work for both people and coding agents, including configuration, output, and failure reporting.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/arize-ai/phoenix/phoenix-cli-development
Any agent
npx skills add Arize-ai/phoenix --skill phoenix-cli-development
Clone the repo
git clone --depth 1 https://github.com/Arize-ai/phoenix

Made for: Claude Code, Codex.

Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,775 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00105 $0.03775
Opus 5 $0.00053 $0.01887
Sonnet 5 $0.00021 $0.00755
Haiku 4.5 $0.00011 $0.00378

Measured 2d ago against content hash f87105a35afd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

phoenix-cli-development 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 2d 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.

js/packages/phoenix-cli/.agents/skills/phoenix-cli-development/SKILL.md · 335 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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.

  1. 2d ago First seen · 335 lines · 105 tokens per session scan A f87105a35afd

Subscribe to this mod's changes

phoenix-cli-development is a skill published in the GitHub repository Arize-ai/phoenix (11,275 stars, last pushed yesterday), with no licence file. It adds 105 tokens to every session and 3,775 once invoked, about $0.0005 per session on Opus 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-08-30.

Related

Other skills, from other repositories

trulens-running-evaluations

Execute TruLens evaluations and view results.

truera/trulens · 15 tokens

api-endpoints

Adding or changing API operations in @repo/operations. One source of truth (defineOperation + a Zod schema) becomes an HTTP endpoint, an OpenAPI operation, an MCP tool, TS + Python SDK methods, a latitude CLI command, and an in-process agent tool — descriptions and contracts must be written with all of these readers…

latitude-dev/latitude-llm · 78 tokens

fix-datadog-issues

Find, triage, and fix production errors captured by Datadog Error Tracking, then open a PR. Use when asked to look at "Datadog issues/incidents/errors", "find and fix bugs from Datadog", investigate the most-frequent or newest production errors, or work a specific Datadog Error Tracking issue.

latitude-dev/latitude-llm · 76 tokens

web-frontend

When to use: apps/web UI — routes, @repo/ui, TanStack Start server functions and collections, navigation (Link vs useNavigate), forms (useForm with createFormSubmitHandler + fieldErrorsAsStrings when Zod validation errors should appear on fields), Tailwind layout rules, design-system updates, and useEffect /…

latitude-dev/latitude-llm · 67 tokens

database-postgres

Drizzle schema, repositories, RLS, SqlClient wiring, Postgres migrations, psql / reset, or platform mappers (toDomain / toInsertRow).

latitude-dev/latitude-llm · 39 tokens

notifications

Multi-channel notifications. Adding a new notification kind, group, or channel; in-app + email delivery; per-user prefs; project-level gates; idempotency.

latitude-dev/latitude-llm · 35 tokens