build

A build-and-install command for the ppxai program, its command-line binaries, desktop integration, and Visual Studio Code extension.

In plain words
What is it for?
Use it to build binaries, package and install the Visual Studio Code extension, or install desktop integration on Linux.
Why use it?
It avoids manually choosing platform-specific build commands, output locations, and installation steps.

Command for Claude Code

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/rcconsult/ppxai/build
Clone the repo
git clone --depth 1 https://github.com/rcconsult/ppxai

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,075 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.00000 $0.01075
Opus 5 $0.00000 $0.00537
Sonnet 5 $0.00000 $0.00215
Haiku 4.5 $0.00000 $0.00108

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

Security

Grade A, and why

build 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 3d 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.

.claude/commands/build.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Build and Install

Build ppxai binaries and VSCode extension for the current platform and install locally.

Arguments

  • $ARGUMENTS - Optional: binaries, extension, desktop, or all (default: all)

Usage

Build and install everything:

/build
/build all

Build only binaries:

/build binaries

Build only VSCode extension:

/build extension

Install desktop integration (Linux only):

/build desktop

Platform Detection

The skill automatically detects the current platform and uses appropriate commands:

Windows

  • Binaries location: ~/.ppxai/bin/
  • Build command: pyinstaller with SSL cert for corporate proxy
  • Outputs: ppxai.exe, ppxaide.exe, ppxai-server.exe, ppxai-desktop.exe

macOS / Linux

  • Binaries location: ~/.local/bin/
  • Build command: pyinstaller
  • Outputs: ppxai, ppxaide, ppxai-server, ppxai-desktop

VSCode Extension

  • Build: npm run compile && npx vsce package
  • Install: code --install-extension ppxai-{version}.vsix --force

Build Steps

1. Build Binaries (if requested)

Windows:

SSL_CERT_FILE="C:/.ssh/Fortinet_CA_SSL.cer" .uv/uv run pyinstaller ppxai.spec --noconfirm
SSL_CERT_FILE="C:/.ssh/Fortinet_CA_SSL.cer" .uv/uv run pyinstaller ppxaide.spec --noconfirm
SSL_CERT_FILE="C:/.ssh/Fortinet_CA_SSL.cer" .uv/uv run pyinstaller ppxai-server.spec --noconfirm
SSL_CERT_FILE="C:/.ssh/Fortinet_CA_SSL.cer" .uv/uv run pyinstaller ppxai-desktop.spec --noconfirm

macOS/Linux:

uv run pyinstaller ppxai.spec --noconfirm
uv run pyinstaller ppxaide.spec --noconfirm
uv run pyinstaller ppxai-server.spec --noconfirm
uv run pyinstaller ppxai-desktop.spec --noconfirm

2. Install Binaries

Windows:

mkdir -p "$USERPROFILE/.ppxai/bin"
cp dist/ppxai.exe "$USERPROFILE/.ppxai/bin/"
cp dist/ppxaide.exe "$USERPROFILE/.ppxai/bin/"
cp dist/ppxai-server.exe "$USERPROFILE/.ppxai/bin/"
cp dist/ppxai-desktop.exe "$USERPROFILE/.ppxai/bin/"

Read the full file on GitHub · 147 lines

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. 3d ago First seen · 147 lines · 0 tokens per session scan A 06ca057f83a1

Subscribe to this mod's changes

build is a command published in the GitHub repository rcconsult/ppxai (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,075 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-31.