Project Starter is a workflow plugin that equips coding agents with specialized subagents, reusable skills, commands, hooks, and output styles for software projects. It is for developers who want structured assistance with tasks such as planning, debugging, code review, security, and automation across several coding-agent platforms. Catalogue add-ons are components of its own workflow.
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/cloudai-x/claude-workflow-v2/dependency-upgradegit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2Wrote 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/cloudai-x/claude-workflow-v2/dependency-upgrade)<a href="https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/dependency-upgrade"><img src="https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/dependency-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 | $0.00019 | $0.01206 |
| Opus 5 | $0.00010 | $0.00603 |
| Sonnet 5 | $0.00004 | $0.00241 |
| Haiku 4.5 | $0.00002 | $0.00121 |
Grade A, and why
dependency-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 5d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Upgrade
Safely upgrade dependencies one at a time with testing between each upgrade.
Context
- Package manager detection: !
ls package-lock.json 2>/dev/null && echo "npm" || ls yarn.lock 2>/dev/null && echo "yarn" || ls pnpm-lock.yaml 2>/dev/null && echo "pnpm" || ls bun.lockb 2>/dev/null && echo "bun" || ls Cargo.toml 2>/dev/null && echo "cargo" || ls go.mod 2>/dev/null && echo "go" || ls requirements.txt pyproject.toml 2>/dev/null && echo "pip/uv" || echo "Unknown" - Current branch: !
git branch --show-current - Working tree status: !
git status --short - Node version (if applicable): !
node --version 2>/dev/null || echo "N/A" - Python version (if applicable): !
python3 --version 2>/dev/null || echo "N/A"
Workflow
Phase 1: Detect Environment
- Identify the package manager from context above
- Confirm a clean working tree (stash or commit uncommitted changes first)
- Ensure tests pass BEFORE any upgrades — this is the baseline:
- Node.js:
npm test/yarn test/pnpm test/bun test - Python:
pytest/python -m pytest - Rust:
cargo test - Go:
go test ./...
- Node.js:
- If baseline tests fail, STOP and report — do not upgrade on a broken baseline
Phase 2: List Outdated Dependencies
Run the appropriate outdated command:
- npm:
npm outdated --json - yarn:
yarn outdated - pnpm:
pnpm outdated - bun:
bun outdated - pip/uv:
uv pip list --outdatedorpip list --outdated --format=json - cargo:
cargo outdated(if installed) or check Cargo.toml - go:
go list -m -u all
Phase 3: Categorize Updates
Sort dependencies into risk categories:
## Outdated Dependencies
### Patch Updates (safe — bug fixes only)
| Package | Current | Latest | Notes |
|---------|---------|--------|-------|
| ... | ... | ... | ... |
### Minor Updates (review — new features, possible deprecations)
| Package | Current | Latest | Notes |
|---------|---------|--------|-------|
| ... | ... | ... | ... |
### Major Updates (careful — breaking changes expected)
| Package | Current | Latest | Notes |
|---------|---------|--------|-------|
| ... | ... | ... | ... |
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.
- 5d ago First seen · 130 lines · 19 tokens per session scan A b48983348638
dependency-upgrade is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 10d ago), licensed MIT. It adds 19 tokens to every session and 1,206 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
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
init
Initialize configurations for Supabase local development.
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.