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.
npx agentmods add skills/arize-ai/arize-claude-code-plugin/arize-projectsnpx skills add Arize-ai/arize-claude-code-plugin --skill arize-projectsgit clone --depth 1 https://github.com/Arize-ai/arize-claude-code-pluginWhat 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 | $0.00073 | $0.02440 |
| Opus 5 | $0.00036 | $0.01220 |
| Sonnet 5 | $0.00015 | $0.00488 |
| Haiku 4.5 | $0.00007 | $0.00244 |
Grade A, and why
arize-projects 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.
How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arize AX Projects
Manage projects in the Arize AI platform using the ax CLI.
Prerequisites
The user must have:
- Arize AX CLI installed (
pip install arize-ax-cli) - CLI configured with valid credentials (
ax config init)
Core Project Commands
List Projects
ax projects list
Options:
--space-id <id>- Space ID to list projects from (uses config default if not set)--limit, -n <count>- Maximum number of projects to return (default: 15)--cursor <token>- Pagination cursor for next page--output, -o <format>- Output format:table(default),json,csv,parquet, or a file path--profile, -p <name>- Configuration profile to use--verbose, -v- Enable verbose logs
Examples:
# List projects (default table format)
ax projects list
# List as JSON
ax projects list --output json
# List from a specific space
ax projects list --space-id sp_abc123
# Limit results
ax projects list -n 5
# Use production profile
ax projects list --profile production
Extracting Project IDs:
# Get all project IDs and names as JSON
ax projects list --output json | jq '.[] | {id: .id, name: .name}'
# Find a project ID by name
ax projects list --output json | jq -r '.[] | select(.name == "My Project") | .id'
# Save project ID to a variable
PROJECT_ID=$(ax projects list --output json | jq -r '.[] | select(.name == "My Project") | .id')
echo "Found project: $PROJECT_ID"
Without jq (using grep):
# Find project by name
ax projects list --output json | grep -B 1 '"name": "My Project"' | grep "id" | cut -d'"' -f4
Resolving Project Names to IDs
The CLI commands (get, delete) require a project ID, not a name. When a user refers to a project by name, resolve the ID first using projects list:
- Run
ax projects list --output json - Parse the JSON to find the project matching the requested name
- Use the resolved ID for subsequent commands
If no exact match is found, check for partial or case-insensitive matches and confirm with the user before proceeding. If multiple matches exist, present the options and ask the user to choose.
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.
- 2d ago First seen · 330 lines · 73 tokens per session scan A 37f865eb8922
arize-projects is a skill published in the GitHub repository Arize-ai/arize-claude-code-plugin (21 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 2,440 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.