A release workflow for building, installing, and publishing the pikiclaw command-line program. It handles versioning, building, local linking, verification, source-control release steps, and release notes.

Use it to build and install pikiclaw locally, update its binary, release a new version, or publish it. After the automated release, use it to prepare categorized notes for the GitHub release.

It groups the steps needed to turn code changes into an installed or published release. It also provides a way to diagnose failed release runs and summarize user-facing changes.

install — Skill by xiaotonng

Install

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.

agentmods

npx agentmods add skills/xiaotonng/pikiloom/install

Any agent

npx skills add xiaotonng/pikiloom --skill install

Clone the repo

git clone --depth 1 https://github.com/xiaotonng/pikiloom

Made for: Claude Code, Codex.

Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 474 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00039	$0.00474
Opus 5	$0.00019	$0.00237
Sonnet 5	$0.00008	$0.00095
Haiku 4.5	$0.00004	$0.00047

Measured 3d ago against content hash f4e0ec63f5d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.pikiloom/skills/install/SKILL.md · 53 lines

What it actually says

Install & Publish pikiclaw

1. Run the release script

./scripts/release.sh

This script handles: version bump -> build -> npm link -> verify -> git commit/tag/push -> wait for CI.

If the script fails, diagnose and fix the issue, then re-run it.

2. Write release notes

After CI creates the GitHub Release, update it with meaningful release notes:

Run git log v<previous-version>..v<new-version> --oneline --no-merges to collect all commits since the last release.
Summarize changes into categories (use only relevant ones, skip empty categories):
- New Features - new user-facing functionality
- Improvements - enhancements to existing features
- Bug Fixes - resolved issues
- Internal - refactors, dependency updates, CI changes
Write concise, user-friendly descriptions (not raw commit messages).

Update the GitHub Release using:

gh release edit v<new-version> --notes "$(cat <<'EOF'
## What's Changed

### New Features
- description of feature

### Bug Fixes
- description of fix

**Full Changelog**: https://github.com/xiaotonng/pikiclaw/compare/v<previous-version>...v<new-version>
EOF
)"

Verify the release notes look correct: gh release view v<new-version>.

Notes

npm link creates a global symlink - rebuild with npm run build after code changes.
The files field in package.json controls what gets published: dist/, LICENSE, README.md.
CI pipeline (.github/workflows/release.yml): builds, publishes to npm, and creates GitHub Release on v* tag push.
To uninstall locally: npm unlink -g pikiclaw.

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.

3d ago First seen · 53 lines · 39 tokens per session scan A f4e0ec63f5d5

Subscribe to this mod's changes

install is a skill published in the GitHub repository xiaotonng/pikiloom (293 stars, last pushed 9d ago), licensed MIT. It adds 39 tokens to every session and 474 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.

DevOps and cloud Git and workflow Releases ai claude cli codex coding nodejs

release-publish

Publish a new AlphaClaw release to npm and GitHub. Use when the user asks to cut a release, publish a version, write release notes, draft a release tweet, or close issues addressed in a release. Covers git history analysis, release note drafting, npm publishing, GitHub release creation, issue closing, and tweet…

chrysb/alphaclaw · 72 tokens

install

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Install & Publish pikiclaw

1. Run the release script

2. Write release notes

Notes

What this file has done since we first saw it

Other skills, from other repositories

release-publish

version-upgrade

release-beta

linear-release-setup

publish-plugins

preflight