setup

A setup command for the Pi coding agent that checks whether it is installed, shows available models, and can manage a review setting used when jobs stop.

In plain words
What is it for?
Checking Pi readiness, viewing configured models, installing Pi when appropriate, and optionally changing the stop-time review gate.
Why use it?
It identifies missing installation or model-provider configuration before you try to use Pi. If Pi is unavailable, it can offer to install it when the required tools are present.

Command

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 commands/agents365-ai/pi-plugin-cc/setup
Clone the repo
git clone --depth 1 https://github.com/Agents365-ai/pi-plugin-cc
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00021 $0.00312
Opus 5 $0.00010 $0.00156
Sonnet 5 $0.00004 $0.00062
Haiku 4.5 $0.00002 $0.00031

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

Security

Grade A, and why

setup 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.

plugins/pi/commands/setup.md · 38 lines

What it actually says

Run:

node "${CLAUDE_PLUGIN_ROOT}/scripts/pi-companion.mjs" setup --json $ARGUMENTS

If the result says Pi is unavailable and npm is available:

  • Use AskUserQuestion exactly once to ask whether Claude should install Pi now.
  • Put the install option first and suffix it with (Recommended).
  • Use these two options:
    • Install Pi (Recommended)
    • Skip for now
  • If the user chooses install, run:
npm install -g --ignore-scripts @earendil-works/pi-coding-agent
  • Then rerun:
node "${CLAUDE_PLUGIN_ROOT}/scripts/pi-companion.mjs" setup --json $ARGUMENTS

If Pi is already installed or npm is unavailable:

  • Do not ask about installation.

Output rules:

  • Present the final setup output to the user.
  • If installation was skipped, present the original setup output.
  • If Pi is installed but no provider is configured, preserve the guidance to set a provider API key (e.g. DEEPSEEK_API_KEY) or write ~/.pi/agent/models.json per pi's providers.md.
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 · 38 lines · 21 tokens per session scan A 6dd4e1688935

Subscribe to this mod's changes

setup is a command published in the GitHub repository Agents365-ai/pi-plugin-cc (43 stars, last pushed 18d ago), licensed Apache-2.0. It adds 21 tokens to every session and 312 once invoked, about $0.0001 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.