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-solo/releasenpx skills add HazAT/pi-solo --skill releasegit clone --depth 1 https://github.com/HazAT/pi-soloWrote 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-solo/release)<a href="https://agentmods.dev/skills/hazat/pi-solo/release"><img src="https://agentmods.dev/badge/skills/hazat/pi-solo/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.00036 | $0.00864 |
| Opus 5 | $0.00018 | $0.00432 |
| Sonnet 5 | $0.00007 | $0.00173 |
| Haiku 4.5 | $0.00004 | $0.00086 |
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.
This is a copy
89% identical to release — 32 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 144 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-solo@v<VERSION>
```
Or latest:
```bash
pi install git:github.com/HazAT/pi-solo
```
Then add the grouped commit sections below it.
Example output:
## ✨ Features
- Idle-close the helper subprocess so it stops appearing under Pi's row in Solo
- Render Solo keyboard shortcut hints on spawn/start/restart/status results
## 🐛 Bug Fixes
- Don't crash when MCP is disabled in Solo settings — poll for re-enable
- Handle tools with empty inputSchema
Step 3: Run Tests
Before tagging, confirm the unit tests pass:
npm test
Stop and surface failures if anything is red.
Step 4: Update package.json
Bump the version in package.json:
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 · 144 lines · 36 tokens per session scan A f255c1ea0bb6
release is a skill published in the GitHub repository HazAT/pi-solo (46 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 864 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to release, differing in 32 lines, and is treated as a copy.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
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
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…