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/minmax/pi-cli-mcp/validationnpx skills add minmax/pi-cli-mcp --skill validationgit clone --depth 1 https://github.com/minmax/pi-cli-mcpWhat 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.00056 | $0.00758 |
| Opus 5 | $0.00028 | $0.00379 |
| Sonnet 5 | $0.00011 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
validation 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 yesterday.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validation
Two hooks, three checks. The set is deliberately small: a hook that takes real time gets bypassed
with --no-verify, and then it does not exist.
npm run hooks # once per clone — points core.hooksPath at .githooks/
Not wired into prepare: that also runs for anyone installing this package from git, and their
hooks are not ours to configure.
pre-commit — seconds
| check | why it exists |
|---|---|
biome check . |
formatting and lint. A package.json written with spaces instead of tabs broke npm run check once. |
| lock regeneration | npm install --package-lock-only and refuse if package-lock.json moved. |
The lock check earns its place because nothing else catches it: npm ci accepts a lock that has
drifted from package.json — verified on a clean clone of a tag whose lock was two minor versions
behind. It rotted from 0.3.0 onward, bin still pointing at index.mjs long after the file was
gone, and went out inside a release tag.
When it fires, the lock has already been regenerated for you. Review it, stage it, commit again.
pre-push — the whole suite
npm test — Vitest plus the type tests. This is the run that compares our view of pi's wire
contract against the installed @earendil-works/pi-* types; see the pi-contract skill. It is the
last gate before anything leaves the machine.
Checks that were considered and dropped
Kept out on purpose, so the list stays worth reading:
| rejected | reason |
|---|---|
"no version literal in src/" |
the handshake version is read from package.json now — the duplicate cannot come back by accident |
*.tgz / stray-file guard |
one line in .gitignore does it; a hook adds nothing |
| "no orphaned processes after tests" | already asserted by child_then_answer in test/lifecycle.test.ts |
npm run build in pre-push |
compilation is covered by the type check; prepare and CI build anyway |
a separate tsc --noEmit in pre-commit |
duplicates the typecheck inside npm test |
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.
- yesterday First seen · 62 lines · 56 tokens per session scan A e47f2da4dd94
validation is a skill published in the GitHub repository minmax/pi-cli-mcp (0 stars, last pushed 9d ago), licensed MIT. It adds 56 tokens to every session and 758 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…