Borrowing it
Nothing to install: this file belongs to mrclrchtr/supi. 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/mrclrchtr/supi/main/.pi/skills/pi-upgrade/SKILL.mdgit clone --depth 1 https://github.com/mrclrchtr/supiWrote 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/mrclrchtr/supi/pi-upgrade)<a href="https://agentmods.dev/skills/mrclrchtr/supi/pi-upgrade"><img src="https://agentmods.dev/badge/skills/mrclrchtr/supi/pi-upgrade/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/skills/mrclrchtr/supi/pi-upgrade"><img src="https://agentmods.dev/badge/skills/mrclrchtr/supi/pi-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 71 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00090 | $0.01320 |
| Opus 5 | $0.00045 | $0.00660 |
| Sonnet 5 | $0.00018 | $0.00264 |
| Haiku 4.5 | $0.00009 | $0.00132 |
Grade A, and why
pi-upgrade 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 4d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PI Upgrade Advisor
Upgrade pi framework dependencies, migrate legacy package names, and surface the new patterns available in the latest release.
Prerequisites
- GitHub CLI (
gh) must be installed and authenticated. - A
package.jsoncontaining either@earendil-works/pi-coding-agentor@earendil-works/pi-tui(legacy@mariozechner/*names also work).
What the script does
The bundled helper (scripts/check-pi-version) handles the mechanical work:
- Detects the current pi package version from
package.json, lockfiles, ornode_modules - Fetches release delta from
earendil-works/piviagh - Bumps version ranges across workspace
package.jsonfiles - Migrates
@mariozechner/pi-*entries to@earendil-works/pi-* - Runs the detected package manager install
- Returns structured JSON with the current version, latest version, release notes, bumped files, and install status
Dry-run is the default recommendation. The helper applies changes when run
without --dry-run, so ask the user which mode to use before invoking it.
Resolve scripts/check-pi-version relative to this SKILL.md file's directory;
do not assume the target project contains .pi/skills/pi-upgrade.
# Preview only (recommended/default)
bash "<skill-dir>/scripts/check-pi-version" --dry-run [path/to/package.json]
# Bump + install + report (only after the user chooses direct apply)
bash "<skill-dir>/scripts/check-pi-version" [path/to/package.json]
What YOU do after the helper runs
- Analyze the installed docs — Read the installed
pi-coding-agentREADME,docs/*.md, and type definitions for new features, APIs, patterns, and deprecations. - Map findings to the user's codebase — Look at the repo's existing pi extensions, skills, or config and point to specific files that could benefit.
- Generate actionable recommendations — Explain what changed, what broke, what was renamed, and what the user should do next.
Workflow
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +2 lines 9d80da113eed
- 9d ago First seen · 144 lines · 90 tokens per session scan A eb7b3352b895
pi-upgrade is a skill published in the GitHub repository mrclrchtr/supi (89 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,320 once invoked, about $0.0005 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.
Other skills, from other repositories
review
Review a change for correctness, security, and missing tests.
gh-address-comments
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
pi-parity-review
Adversarially verify that a ported change is faithful to the original pi implementation (TS source + published npm build). Use after porting upstream pi changes, or standalone on any area of this repo ("is X faithful to pi?").
pi-go-review
Review ported Go code for idiomatic quality — that the port maximizes Go rather than transliterating TypeScript. Use after porting upstream pi changes, or standalone on any diff in this repo.
review-pr
Deeply review a GitHub pull request.
review-agent
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.