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/hazat/pi-interactive-subagents/releasenpx skills add HazAT/pi-interactive-subagents --skill releasegit clone --depth 1 https://github.com/HazAT/pi-interactive-subagentsWrote 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/hazat/pi-interactive-subagents/release)<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="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 | $0.00036 | $0.00822 |
| Opus 5 | $0.00018 | $0.00411 |
| Sonnet 5 | $0.00007 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release — 89% identical, 32 lines differ
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).0major→ (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
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 First seen · 134 lines · 36 tokens per session scan A 75921daf7d2d
release is a skill published in the GitHub repository HazAT/pi-interactive-subagents (667 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 822 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
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
mate-oss-gate
在准备把 MateCloud（或其子集）开源 / 发布到公开仓前使用。按 open-core 边界把关：剥离企业代码、清竞品名与内部路径、查密钥、确认 LICENSE。当用户说"要开源了""发布公开版""开源前检查""oss release"时触发。.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".