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/phantom/phantom-connect-sdk/new-cli-actionnpx skills add phantom/phantom-connect-sdk --skill new-cli-actiongit clone --depth 1 https://github.com/phantom/phantom-connect-sdkWhat 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.00065 | $0.02923 |
| Opus 5 | $0.00032 | $0.01461 |
| Sonnet 5 | $0.00013 | $0.00585 |
| Haiku 4.5 | $0.00006 | $0.00292 |
Grade A, and why
new-cli-action 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/new-cli-action — Scaffold a New CLI Action
Arguments passed: $ARGUMENTS
You are helping the user add a new command to the Phantom CLI (packages/cli). Every action is automatically exposed in three places: the CLI binary, the MCP server, and OpenClaw. All three come for free from a single createAction call — the user only needs to write one file and make two registration edits.
Framework: The CLI is built on incur, a TypeScript framework for building CLIs that work as both binaries and MCP servers. The
Cliandzimports in every action file come fromincur. If you need deeper guidance on incur patterns — schemas, Cli APIs, or advanced usage — runnpx incur skills addin the project root to pull the official incur skill into Claude Code and piggyback off it.
Step 1 — Understand the requirement
If $ARGUMENTS is empty or vague, ask the user:
- What should the command do? (one sentence)
- What inputs does it need?
- What does a success response look like?
- Where should it live in the CLI? (top-level like
phantom buy, or under a sub-group likephantom perps open)
If $ARGUMENTS describes the command well enough, proceed directly.
Step 2 — Determine the file location and CLI group
The CLI is structured as follows. Read packages/cli/src/index.ts and the relevant command file to confirm the current shape before writing anything.
| CLI path | Command file | Action files |
|---|---|---|
phantom <cmd> |
src/index.ts (registered directly) |
src/actions/<name>.ts |
phantom wallet <cmd> |
src/commands/wallet.ts |
src/actions/<name>.ts |
phantom solana <cmd> |
src/commands/solana.ts |
src/actions/<name>.ts |
phantom evm <cmd> |
src/commands/evm.ts |
src/actions/<name>.ts |
phantom perps <cmd> |
src/commands/perps.ts |
src/actions/<name>.ts |
phantom token <cmd> |
src/commands/token.ts |
src/actions/<name>.ts |
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 · 281 lines · 65 tokens per session scan A 8e661cf59214
new-cli-action is a skill published in the GitHub repository phantom/phantom-connect-sdk (159 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 2,923 once invoked, about $0.0003 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.