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/feniix/pi-extensions/releasenpx skills add feniix/pi-extensions --skill releasegit clone --depth 1 https://github.com/feniix/pi-extensionsWrote 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/feniix/pi-extensions/release)<a href="https://agentmods.dev/skills/feniix/pi-extensions/release"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/release.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.00038 | $0.00880 |
| Opus 5 | $0.00019 | $0.00440 |
| Sonnet 5 | $0.00008 | $0.00176 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
release 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 5d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
Automates release: analyze commits, bump version, generate changelog, commit, push, and create GitHub release.
Tool Restrictions (Critical)
Use ONLY these tools:
devtools_get_repo_info- Verify the active worktree branch and statusdevtools_check_ci- Check CI status on the default branchdevtools_get_latest_tag- Get current versiondevtools_analyze_commits- Analyze commits for version bumpdevtools_bump_version- Update package.jsondevtools_commit- Commit version bumpdevtools_push- Push changesdevtools_create_release- Create GitHub release
Preconditions
Verify these before starting in Pi's active working directory:
- The active worktree is on the repository's default branch (
devtools_get_repo_info) - The active working tree is clean (no uncommitted changes)
- CI is passing on the default branch (
devtools_check_ci)
The default branch may already be checked out in another worktree. If the active worktree is not on it, stop and explain which worktree context is active; do not switch branches or modify the other worktree. If any precondition fails, stop and explain.
Process
Step 1: Analyze Commits
Call devtools_analyze_commits to:
- Find commits since last tag
- Determine bump type (major/minor/patch)
- Get suggested new version
Present to user:
- Show commits grouped by type
- Show suggested version bump
- Ask for confirmation or override
Step 2: Bump Version
After user confirms:
- Call
devtools_bump_versionwith new version - Show the change to user
Step 3: Generate Changelog
Create changelog from commit analysis:
- Group commits by type (Features, Fixes, Other)
- Capitalize first letter
- Keep concise
Present for user review and approval.
Step 4: Commit and Push
- Commit with message:
chore: bump version to vX.Y.Z - Call
devtools_push
Step 5: Create Release
Call devtools_create_release with:
- Tag:
vX.Y.Z - Title:
vX.Y.Z - Body: Generated changelog
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.
- 5d ago First seen · 122 lines · 38 tokens per session scan A 8f1a2cfc67f4
release is a skill published in the GitHub repository feniix/pi-extensions (23 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 880 once invoked, about $0.0002 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
pi-package-sandbox-test
Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.
pi-release-workflow
Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.
pi-review-gated-delivery
Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.
create-draft-pr
Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.
create-pr
Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.
helmor-release
Prepare Helmor releases by inspecting the current branch, drafting a concise user-facing Changesets entry first (bump + body — keep it as short as possible), creating any needed pending in-app release announcement under .announcements/, and then showing the user the result with a short menu of adjustments they can…