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/modelengine-group/fit-framework/upgrade-dependencynpx skills add ModelEngine-Group/fit-framework --skill upgrade-dependencygit clone --depth 1 https://github.com/ModelEngine-Group/fit-frameworkWhat 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.00043 | $0.00275 |
| Opus 5 | $0.00022 | $0.00138 |
| Sonnet 5 | $0.00009 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
upgrade-dependency 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.
What it actually says
升级依赖
参数
<package-name>: 包名<from-version>: 原版本<to-version>: 新版本
执行步骤
-
查找依赖文件:
grep -r "<package-name>" --include="pom.xml" --include="package.json" . grep -r "<from-version>" --include="pom.xml" --include="package.json" . -
更新依赖版本:
- Maven (pom.xml): 替换 version 标签
- Node.js (package.json): 更新版本号
-
更新相关静态资源（如 CDN 链接等）。
-
验证变更:
git diff mvn clean package -Dmaven.test.skip=true mvn test -
输出变更摘要。
注意: 升级前检查 CHANGELOG 和 Migration Guide，注意破坏性变更。不要自动 git commit。一次只升级一个依赖。
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 · 38 lines · 43 tokens per session scan A d8056f801298
upgrade-dependency is a skill published in the GitHub repository ModelEngine-Group/fit-framework (2,117 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 275 once invoked, about $0.0002 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
mechanical-engineering-research
Apply source-aware mechanical-engineering judgment to research, analysis, coding, writing, teaching, research identity, and release work. Use for thermal-fluid systems, heat transfer, fluid mechanics, thermodynamics, HVAC, energy systems, turbomachinery, piping, multiphase flow, experiments, correlations, CFD…
swarm
Launching multi-agent parallel work with the Agentic SDLC. Use when a task benefits from decomposition into parallel subtasks.
finish
Completing a development branch for merge readiness. Use when implementation and tests pass and the branch needs formal preparation for review and merge.
grill
Interrogating requirements to validate before building. Use before swarm decomposition, design decisions on ambiguous features, or when scope creep risk is high.
team
Referencing the agent roster, roles, coordination model, and dispatch modes. Use when spawning agents or checking permissions.
ticket
Associate every PDS task with a GitHub issue. Orchestrator finds or creates the ticket, posts plan and acceptance criteria as a checkbox list, updates it as work progresses. Use at Phase 1 of every swarm.