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/ggwhite/4x/releasenpx skills add ggwhite/4x --skill releasegit clone --depth 1 https://github.com/ggwhite/4xWhat 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.00066 | $0.01029 |
| Opus 5 | $0.00033 | $0.00515 |
| Sonnet 5 | $0.00013 | $0.00206 |
| Haiku 4.5 | $0.00007 | $0.00103 |
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 2d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Publish a new 4x version. The CI pipeline (goreleaser + homebrew) triggers on tag push, so the job here is: write accurate release notes, get user approval, then tag and push.
Workflow
1. Determine version
git tag -l 'v*' --sort=-v:refname | head -1
Bump the patch number by default (e.g., v0.1.8 -> v0.1.9). If the user specifies minor or major, bump accordingly.
Show the user: "上個版本是 vX.Y.Z，這次準備發 vA.B.C" and confirm before continuing.
2. Collect changes
git log <last-tag>..HEAD --oneline --no-decorate
If there are zero commits since the last tag, stop and tell the user there's nothing to release.
3. Draft changelog section
Read the existing CHANGELOG.md to match its style. The format follows Keep a Changelog:
## [X.Y.Z] - YYYY-MM-DD
### Fixes
- **Short name** — description of the fix
### Features
- **Short name** — description of the feature
Categorization rules:
fix/bugfixcommits ->### Fixesfeat/ feature commits ->### Featuresci/ workflow commits ->### CIdocscommits ->### Docs(only if user-facing; skip changelog-only docs commits)refactor/perf/chore->### Internal(only if noteworthy; skip trivial ones)
Each item should be a concise, user-facing description — not a raw commit message. Rewrite commit messages into the bold-name-em-dash style. Group related commits into a single item when they address the same thing.
Skip commits that are only changelog/release housekeeping (e.g., "docs: vX.Y.Z changelog").
4. Preview
Show the drafted changelog section to the user in full. Ask: "這樣 OK 嗎？要調整什麼？"
Proceed only after the user approves; if they request changes, revise and show again.
5. Update CHANGELOG.md
Insert the new version section at the top, right after the file header (the "# Changelog" heading and the format description paragraph). Leave existing sections untouched (see Important Rules).
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.
- 2d ago First seen · 128 lines · 66 tokens per session scan A 38c274c549d0
release is a skill published in the GitHub repository ggwhite/4x (33 stars, last pushed 8d ago), licensed MIT. It adds 66 tokens to every session and 1,029 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
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.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
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…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.