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/skills/build-install/SKILL.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/skills/rcconsult/ppxai/build-install)<a href="https://agentmods.dev/skills/rcconsult/ppxai/build-install"><img src="https://agentmods.dev/badge/skills/rcconsult/ppxai/build-install.svg" alt="Measured on agentmods" 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.00114 | $0.07329 |
| Opus 5 | $0.00057 | $0.03664 |
| Sonnet 5 | $0.00023 | $0.01466 |
| Haiku 4.5 | $0.00011 | $0.00733 |
Grade C, and why
build-install scanned grade C with 2 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf build dist Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
for i in $(seq 1 25); do curl -s -m2 -o /dev/null http://127.0.0.1:54320/status && break; sleep 0.5; done How it starts
The opening of the file, as written. The whole thing — 593 lines — stays where its author put it; the contents beside it link to each section on GitHub.
build-install
End-to-end local install of ppxai. Build all binaries + VSCode extension
(+ macOS-only .app and DMG), then install everything to system
locations exactly as a user-side install would. Useful for testing a
branch before release, or for verifying a release artifact after CI
uploads it.
Preconditions
All platforms
- Working tree at the version you want to ship — version files already
bumped (see
tests/test_version_consistency.pyfor the SoT list). uvresolvable per CLAUDE.md "uv Resolution" (system or.uv/uv).- Build venv MUST have the
[data]extras. The office-preview pipeline needspypdfium2(PDF→PNG) +python-pptx/openpyxl, which live in the[data]optional extra. Step 1 runsuv sync --all-extrasto guarantee it. Without it the binaries build fine but ship WITHOUT office support — LibreOffice is detected yetrender_pptx_slidesreturns[]→ "No slides rendered" (caught live 2026-06-14). Matches the CI build (.github/workflows/build.yml) and the release-script test step, both of which use--all-extras. node+npmfor the VSCode extension build.- A POSIX-ish shell. Bash works on all four platforms (macOS native, Linux native, Windows via Git Bash). PowerShell alternatives are noted where they meaningfully simplify Windows-only flows.
Platform-specific
- macOS Apple Silicon — host is arm64.
uname -mprintsarm64.create-macos-app.shwritesppxai-X.Y.Z-macos-arm64.dmg. - macOS Intel — host is x86_64.
uname -mprintsx86_64.create-macos-app.shwritesppxai-X.Y.Z-macos-intel.dmg. The alternatescripts/build-intel.shorchestrates the same flow with upload-to-release support. - Linux —
linux-amd64is the only platform built today. Binaries install to~/.local/bin/(must be on$PATH). - Windows — PyInstaller produces
.exesuffixes automatically. Binaries install to~/.ppxai/bin/(NOT~/.local/bin/; see CLAUDE.md "Installation Locations").~/.ppxai/bin/must be on$env:PATH. Easiest run-shell is Git Bash (matches steps below); PowerShell variants noted where useful.
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.
- 6d ago First seen · 593 lines · 114 tokens per session scan C 0e0476abfeff
build-install is a skill published in the GitHub repository rcconsult/ppxai (5 stars, last pushed 4d ago), licensed MIT. It adds 114 tokens to every session and 7,329 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…