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/363045841/klinechartquant/update-versionnpx skills add 363045841/KLineChartQuant --skill update-versiongit clone --depth 1 https://github.com/363045841/KLineChartQuantWhat 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.00009 | $0.00303 |
| Opus 5 | $0.00005 | $0.00151 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
update-version 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.
What it actually says
- 需要且只要更新以下文件中的版本: @packages\core\package.json @packages\desktop-electron\package.json @packages\core\src\version.ts @packages\vue\package.json
版本格式eg: 0.9.0-alpha.1 // alpha 0.9.0 // 正式版本
- 使用git tag打上版本标签, 版本要带上 v,以触发 @.github\workflows\release.yml 发布npm包
- 一次性读取当前版本tag到上一个tag之间的提交信息，编写release日志，输出到
docs/release/<当前tag>.md（如docs/release/v0.9.4.md），并将该文件与版本变更一起提交，确保 tag 指向的 commit 已包含该文件（否则 release 工作流将回退为自动生成），格式如下，要有中英对照:
相比 [上个tag] 的变更 / Changes since [上个tag]
✨ 新功能 / Features
- 标题: xxx
- title: xxx
🐛 Bug 修复 / Fixes
🏗️ 架构与重构 / Architecture & Refactoring
📚 文档 / Documentation
其中，不包含的项目可以不填。
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 · 31 lines · 9 tokens per session scan A ed3e2f7f055d
update-version is a skill published in the GitHub repository 363045841/KLineChartQuant (21 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 303 once invoked, about $0.0000 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
tinyvue-develop-spec
在当前仓库进行组件的开发，主题开发，国际化开发，测试脚本开发时，必须遵守以下规范。.
update-release-notes
Update the release notes file at apps/docs/content/releases/next.mdx in the tldraw/tldraw repo based on PRs since the previous release, or archive next.mdx to a versioned file when a new version is published.
write-release-notes
Writing release notes articles for tldraw SDK releases. Use when creating new release documentation, drafting release notes from scratch, or reviewing release note quality. Provides guidance on structure, voice, and content for release files in apps/docs/content/releases/.
release
Use when preparing or publishing an NGINX UI release, including version bumping with version.sh, release note drafting, release-prep commits, annotated tags, pushing dev and tags, and creating GitHub Releases with Announcements discussions.
summarize-releases
Create a monthly NVIDIA Elements “What’s New” docs page and a concise, copy-ready summary from local release tags, tagged changelogs, package versions, and commit history. Use for a scheduled release PR, monthly update, release roundup, changelog digest, Slack blurb, announcement, or plain-language explanation of…
dotcom-release-crew
Identify who contributed critical fixes or significant features to this week's dotcom release (the commits on main that are not yet on production) and post a short summary to the #development Discord channel.