Borrowing it
Nothing to install: this file belongs to rcconsult/ppxai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rcconsult/ppxai/master/.claude/commands/build.mdgit clone --depth 1 https://github.com/rcconsult/ppxaiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/rcconsult/ppxai/build)<a href="https://agentmods.dev/commands/rcconsult/ppxai/build"><img src="https://agentmods.dev/badge/commands/rcconsult/ppxai/build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rcconsult/ppxai/build"><img src="https://agentmods.dev/badge/commands/rcconsult/ppxai/build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01233 |
| Opus 5.5 | $0.00000 | $0.00493 |
| Sonnet 5.5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00123 |
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 10d 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 — 156 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, orall(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:
pyinstallerwith 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/"
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.
- 10d ago Changed · +9 lines 1c97807f7c9a
- 1mo ago First seen · 147 lines · 0 tokens per session scan A 06ca057f83a1
build is a command published in the GitHub repository rcconsult/ppxai (6 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,233 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.