pi-interactive-subagents: Skill for Claude Code

.pi/skills/release/SKILL.md

release is a skill for Claude Code, Codex from HazAT/pi-interactive-subagents. It costs 36 tokens per session (822 once invoked), scanned A, original, MIT.

A release workflow for creating a versioned GitHub release and generating a changelog from recent commits. A GitHub release is a published snapshot of a project's code and notes for that version.

In plain words
What is it for?
Use it to bump a project's patch, minor, or major version, group commit changes, and publish release notes.
Why use it?
It removes the manual work of choosing the next version and summarising changes since the previous release.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

This is HazAT/pi-interactive-subagents's own configuration. It tells Claude Code and Codex how to work on pi-interactive-subagents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything pi-interactive-subagents configures →

Reuse

Borrowing it

Nothing to install: this file belongs to HazAT/pi-interactive-subagents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/HazAT/pi-interactive-subagents/main/.pi/skills/release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/HazAT/pi-interactive-subagents

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/hazat/pi-interactive-subagents/release/github.svg)](https://agentmods.dev/skills/hazat/pi-interactive-subagents/release)
Your own site
<a href="https://agentmods.dev/skills/hazat/pi-interactive-subagents/release"><img src="https://agentmods.dev/badge/skills/hazat/pi-interactive-subagents/release/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/hazat/pi-interactive-subagents/release"><img src="https://agentmods.dev/badge/skills/hazat/pi-interactive-subagents/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 822 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

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 →

  • high Tool Misuse · line 116
    Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).
    Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.00822
Opus 5.5 $0.00014 $0.00329
Sonnet 5.5 $0.00007 $0.00164
Haiku 4.5 $0.00004 $0.00082

Measured 2mo ago against content hash 75921daf7d2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • release — 89% identical, 32 lines differ
.pi/skills/release/SKILL.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release

Create a versioned GitHub release with an auto-generated changelog from commits since the last release.

Step 1: Determine Version

Check the current version and latest git tag:

cat package.json | grep '"version"'
git tag -l --sort=-v:refname | head -5

If the user provided a version, use it. Otherwise ask:

What version? (current is X.Y.Z — patch/minor/major, or exact version)

Resolve semver:

  • patch → X.Y.(Z+1)
  • minor → X.(Y+1).0
  • major → (X+1).0.0
  • Exact version string → use as-is

Step 2: Generate Changelog

Get commits since the last tag (or all commits if no tags exist):

# If tags exist:
git log $(git tag -l --sort=-v:refname | head -1)..HEAD --pretty=format:"- %s" --no-merges

# If no tags:
git log --pretty=format:"- %s" --no-merges

Group commits by type using conventional commit prefixes:

Prefix Section
feat ✨ Features
fix 🐛 Bug Fixes
refactor ♻️ Refactoring
docs 📝 Documentation
chore, test, perf, ci 🔧 Other Changes
No prefix 🔧 Other Changes

Format as markdown. Omit empty sections. Strip the type(scope): prefix from each line for readability.

Always start the changelog with this install block (hardcoded):

Install:

```bash
pi install git:github.com/HazAT/pi-interactive-subagents@v<VERSION>
```

Or latest:

```bash
pi install git:github.com/HazAT/pi-interactive-subagents
```

Then add the grouped commit sections below it.

Example output:

## ✨ Features

- Add live subagent status widget
- Make subagent tool async — return immediately, steer on completion

## 🐛 Bug Fixes

- Fix session file collision with 3+ concurrent agents
- Truncate widget lines to terminal width

Step 3: Update package.json

Bump the version in package.json:

# Read, update, write back — don't use npm version (it may auto-commit)

Use a precise edit to change only the version field.

Step 4: Commit, Tag, Push

Read the full file on GitHub · 134 lines

Changes

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.

  1. 2mo ago First seen · 134 lines · 36 tokens per session scan A 75921daf7d2d

Subscribe to this mod's changes

release is a skill published in the GitHub repository HazAT/pi-interactive-subagents (724 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 822 once invoked, about $0.0001 per session on Opus 5.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.