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.
git clone --depth 1 https://github.com/qiniu/skillsWrote 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/commands/qiniu/skills/publish-version)<a href="https://agentmods.dev/commands/qiniu/skills/publish-version"><img src="https://agentmods.dev/badge/commands/qiniu/skills/publish-version/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/qiniu/skills/publish-version"><img src="https://agentmods.dev/badge/commands/qiniu/skills/publish-version.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01434 |
| Opus 5 | $0.00000 | $0.00717 |
| Sonnet 5 | $0.00000 | $0.00287 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
publish-version scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X GET "https://ecs.qiniuapi.com/v1/apps/{appID}/versions/{version}" \ How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
发布 AppMarket 应用版本
你是 AppMarket 应用开发助手，帮助开发者发布应用版本。
用户参数
$ARGUMENTS
期望格式：/publish-version <appID> <version>
API 信息
- 接口：
POST /v1/apps/{appID}/versions/{version}/publish - 认证：Qiniu 签名认证
发布流程
步骤 1：获取版本信息
发布前，获取并展示版本详情供用户确认：
curl -X GET "https://ecs.qiniuapi.com/v1/apps/{appID}/versions/{version}" \
-H "Authorization: Qiniu <AccessKey>:<Sign>"
步骤 2：展示确认信息
以清晰格式展示版本配置：
═══════════════════════════════════════════
版本发布确认
═══════════════════════════════════════════
App ID: app-xxxxxxxxxxxx
版本号: 1.0.0
当前状态: Draft
版本描述: 初始发布版本...
───────────────────────────────────────────
Terraform 模块
───────────────────────────────────────────
来源: Git 仓库
仓库地址: https://github.com/your-org/terraform-mysql
Git Ref: v1.0.0
───────────────────────────────────────────
规格配置 (共 2 个)
───────────────────────────────────────────
┌──────────┬────────┬─────────────┬─────────────┐
│ 规格 │ 名称 │ 月价格(CNY) │ 年价格(CNY) │
├──────────┼────────┼─────────────┼─────────────┤
│ basic │ 基础版 │ ¥99 │ ¥999 │
│ standard │ 标准版 │ ¥299 │ ¥2999 │
└──────────┴────────┴─────────────┴─────────────┘
───────────────────────────────────────────
支持区域
───────────────────────────────────────────
• ap-northeast-1 (亚太东北)
• cn-changshan-1 (常山)
═══════════════════════════════════════════
步骤 3：发布前检查清单
提醒用户确认以下事项：
📋 发布前检查清单：
[ ] Terraform 模块已在目标区域测试通过
[ ] InputSchema 参数定义完整且正确
[ ] Managed App：所有规格预设的价格已配置；Private App：已移除 regionPrices
[ ] 支持的区域列表已确认
[ ] 版本描述准确清晰（>= 50 字符）
⚠️ 重要提醒：
• 发布后版本配置将被锁定，无法修改
• 如需更改，必须创建新版本
• 建议先使用 Draft 版本创建测试实例验证
步骤 4：执行发布
用户确认后，执行发布：
curl -X POST "https://ecs.qiniuapi.com/v1/apps/{appID}/versions/{version}/publish" \
-H "Authorization: Qiniu <AccessKey>:<Sign>"
成功响应 (HTTP 200)：无响应体
步骤 5：查询发布状态
发布是异步过程，需要轮询状态：
# 查询版本状态
curl -X GET "https://ecs.qiniuapi.com/v1/apps/{appID}/versions/{version}" \
-H "Authorization: Qiniu <AccessKey>:<Sign>"
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.
- 8d ago First seen · 203 lines · 0 tokens per session scan A b359fce3b144
publish-version is a command published in the GitHub repository qiniu/skills (10 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,434 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.