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/benedictking/ccx/store-updatenpx skills add BenedictKing/ccx --skill store-updategit clone --depth 1 https://github.com/BenedictKing/ccxWrote 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/benedictking/ccx/store-update)<a href="https://agentmods.dev/skills/benedictking/ccx/store-update"><img src="https://agentmods.dev/badge/skills/benedictking/ccx/store-update.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.00100 | $0.00988 |
| Opus 5 | $0.00050 | $0.00494 |
| Sonnet 5 | $0.00020 | $0.00198 |
| Haiku 4.5 | $0.00010 | $0.00099 |
Grade A, and why
store-update 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCX Desktop Store MSIX 下载与发布公告技能
适用场景
当用户在 GitHub Release 发布完成后,需要下载 Store MSIX 包、校验完整性、生成 Store 更新说明时使用本技能。典型输入:
- "release 后下载两个 msix"
- "帮我准备 Store 的 msix 和更新说明"
- "下载 store msix 并生成发布内容"
- "跑一下 desktop store update"
执行流程
1. 下载 MSIX 并校验
python3 .claude/skills/store-update/scripts/download_store_msix.py --download-dir ./store-msix
脚本会:
- 通过 GitHub API 读取最新 release 信息。
- 从 Release body 生成 Store listing
releaseNotes纯文本预览。 - 用
gh release download下载两个 MSIX(amd64 / arm64)和对应.sha256到指定目录(gh会自动走已登录的 auth,绕过代理)。 - 校验架构集合必须为
amd64+arm64。 - 校验 sha256(如果 release 中存在
.sha256)。 - 输出下载结果摘要、文件路径和手动操作指引。
2. 打开下载目录
下载并校验完成后,用系统命令打开下载目录,便于用户直接拖拽上传:
open ./store-msix
3. 输出手动操作指引
下载完成后,向用户输出以下信息:
- 两个 MSIX 文件的本地路径。
- SHA256 校验结果。
- 从 Release body 生成的 Store 更新说明预览。
- 手动操作指引:
- 打开 Partner Center
- 进入 CCX Desktop → Product release → 点击「Packages」行上传两个 MSIX
- 点击「Store listings」行 → 选择语言 → 在「What's new in this version」粘贴更新说明
- 返回后点击「Submit for certification」
默认产物匹配
当前 release workflow 生成两个 Store MSIX:
CCX-Desktop-${VERSION}-windows-amd64-store.msixCCX-Desktop-${VERSION}-windows-arm64-store.msix
脚本要求最新 GitHub Release 中恰好匹配 amd64 与 arm64 两个 .msix,并优先读取同名 .sha256 进行校验。
常用参数
python3 .claude/skills/store-update/scripts/download_store_msix.py --help
常用选项:
--tag <tag>:指定 release tag,不使用 latest。--allow-prerelease:允许 prerelease Release,默认拒绝。--repo owner/name:指定 GitHub 仓库。--download-dir <dir>:保留下载文件,便于手动上传。默认使用临时目录。--store-release-notes "...":手动覆盖 Store listing 更新内容。--release-notes-file <file>:从本地文件读取 Store listing 更新内容。--no-release-notes:不生成 Store listing releaseNotes 预览。--release-notes-max-chars 1000:Store 更新内容最大长度,默认 1000。--truncate-release-notes:超过长度时显式截断;默认超过长度会失败,避免静默丢内容。
输出要求
完成后输出中文摘要,至少包含:
- GitHub release tag 和 URL。
- Store 更新内容来源、长度和预览。
- 两个 MSIX 文件名、架构、本地路径和 sha256 校验状态。
- 手动上传指引(Partner Center 入口和操作步骤)。
- 如果失败,保留错误摘要。
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 95 lines · 100 tokens per session scan A 07c044ab8974
store-update is a skill published in the GitHub repository BenedictKing/ccx (3,966 stars, last pushed 3d ago), licensed MIT. It adds 100 tokens to every session and 988 once invoked, about $0.0005 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
docs-changelog
Generates and formats changelog files for a new release based on provided version and raw changelog data.
bump-version
Use when bumping the AionUi version: query AionCore release, verify artifacts, update package.json, generate CHANGELOG, branch, commit, push, create PR, auto-merge, tag release.
release
Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.
changelog
Generate or update the CHANGELOG.md for a new release version. Use when the user says "generate changelog", "update changelog", "write release notes", or asks to prepare a changelog for a version like "changelog for 0.5.3".
release
Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…
version-release
Version release workflow — release process and GitHub Release notes (not docs/changelog pages).