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 commands/echovic/boss-skill/boss-upgradegit clone --depth 1 https://github.com/echoVic/boss-skillWrote 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/echovic/boss-skill/boss-upgrade)<a href="https://agentmods.dev/commands/echovic/boss-skill/boss-upgrade"><img src="https://agentmods.dev/badge/commands/echovic/boss-skill/boss-upgrade.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.1 | $0.00020 | $0.00405 |
| Opus 5 | $0.00010 | $0.00202 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
boss:upgrade 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 6d 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
/boss:upgrade — 升级 Boss Skill
升级 @blade-ai/boss-skill npm 包到最新版本，并将最新的 hooks 配置同步到当前项目。
执行步骤
- 检查当前安装的版本
- 运行
npm update @blade-ai/boss-skill升级到最新版 - 运行
npx boss-skill install重新安装 hooks 到.claude/settings.json - 显示升级前后的版本和变更摘要
用法
/boss:upgrade
执行脚本
echo "📦 正在检查当前版本..."
OLD_VERSION=$(node -e "try{console.log(require('@blade-ai/boss-skill/package.json').version)}catch{console.log('未安装')}" 2>/dev/null)
echo " 当前版本: $OLD_VERSION"
echo ""
echo "⬆️ 正在升级..."
npm update @blade-ai/boss-skill 2>&1
NEW_VERSION=$(node -e "try{console.log(require('@blade-ai/boss-skill/package.json').version)}catch{console.log('升级失败')}" 2>/dev/null)
echo " 最新版本: $NEW_VERSION"
if [ "$OLD_VERSION" = "$NEW_VERSION" ]; then
echo ""
echo "✅ 已是最新版本 ($NEW_VERSION)，无需升级"
else
echo ""
echo "🔄 正在同步 hooks..."
npx boss-skill install
echo ""
echo "✅ 升级完成: $OLD_VERSION → $NEW_VERSION"
fi
echo ""
echo "📂 Skill 路径: $(npx boss-skill path)"
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.
- 6d ago First seen · 52 lines · 20 tokens per session scan A c4989396ed4d
boss:upgrade is a command published in the GitHub repository echoVic/boss-skill (553 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 405 once invoked, about $0.0001 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 commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
init
Initialize configurations for Supabase local development.
tokenless-stats
Show Tokenless compression statistics.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.