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/firstp1ck/pi-coding-agent-forge/release-aurnpx skills add Firstp1ck/pi-coding-agent-forge --skill release-aurgit clone --depth 1 https://github.com/Firstp1ck/pi-coding-agent-forgeWhat 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.00057 | $0.01469 |
| Opus 5 | $0.00028 | $0.00734 |
| Sonnet 5 | $0.00011 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
release-aur 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 3d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release AUR
Use this skill for AUR package creation, updates, release readiness reviews, publishing decisions, and /release-aur-setup prerequisite workflows.
Mandatory workflow
- Start with
/release-aur plan <target>unless the user explicitly asks only to create a repo. - Review the generated preflight output and inspect files when needed:
PKGBUILD.SRCINFOgit status --porcelain=v1git diff -- PKGBUILD .SRCINFOgit diff --cachedif anything is staged
- Confirm these gates before GO:
makepkg --printsrcinfosucceeds..SRCINFOis present or will be regenerated by publish mode.makepkg --verifysourcesucceeds.- full
makepkgbuild/check/package succeeds. - no
namcap E:findings unless the user explicitly accepts a justified exception. - no build artifacts, secrets, or unrelated files are staged or likely to be auto-staged.
- dependencies are direct and explicit, not merely transitive.
- latest-release update check ran against the configured source (global/per-package/auto) or was explicitly skipped with justification.
pkgvermatches upstream andpkgrelis reset to1when upstreampkgveris bumped.- checksum arrays were refreshed with
updpkgsumsafter a version bump. - VCS packages are not committed for a mere upstream
pkgverbump.
- Return
GOonly when publish is appropriate. Include the exact command:/release-aur publish <target> - Return
NO-GOwith exact fixes when any blocker remains. - Never push manually with raw
git pushunless the user explicitly bypasses the package workflow. Prefer/release-aur publishbecause it regenerates.SRCINFO, stages conservatively, commits, and pushes to AURmaster.
Setup flow
Use /release-aur-setup when the user needs AUR release workflow prerequisites prepared. The setup workflows are:
/release-aur-setup dir [path-to-aur-repos]
/release-aur-setup source [global <source>|package <pkgbase> <source>|clear <pkgbase>|status]
/release-aur-setup ssh
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.
- 3d ago First seen · 110 lines · 57 tokens per session scan A d41a23df8291
release-aur is a skill published in the GitHub repository Firstp1ck/pi-coding-agent-forge (74 stars, last pushed 3d ago), licensed MIT. It adds 57 tokens to every session and 1,469 once invoked, about $0.0003 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
commit-pr
Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before git push, gh pr create, gh pr edit, or gh pr ready. Routes to the single…
ship-it
Code commit, PR creation, merge, and issue closure workflow via GitHub CLI (gh). Triggers after a goal (GitHub Issue) implementation is complete — commit code, push branch, create PR, merge, then close the issue. Use when the user says "提交代码", "commit and merge", "创建PR", "合入", "关闭issue", "ship-it", or when a goal…
os-eco-dep-sync
Bump warren onto the latest published @os-eco/ versions across package.json + bun.lock and the Dockerfile CLI pins, then run the gates and open a PR. Use when checking if warren is on the newest burrow/plot/canopy/seeds/mulch/sapling.
release
Prepare, cut, and verify a warren release — tracker audits, version bump, CHANGELOG curation, ROADMAP update, push, then watch the pipeline through to published artifacts.
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…