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/dailybothq/deepworkplan-skill/dependency-upgradenpx skills add DailybotHQ/deepworkplan-skill --skill dependency-upgradegit clone --depth 1 https://github.com/DailybotHQ/deepworkplan-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/skills/dailybothq/deepworkplan-skill/dependency-upgrade)<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/dependency-upgrade"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/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.00152 | $0.01978 |
| Opus 5 | $0.00076 | $0.00989 |
| Sonnet 5 | $0.00030 | $0.00396 |
| Haiku 4.5 | $0.00015 | $0.00198 |
Grade A, and why
deepworkplan-addon-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 4d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepWorkPlan — Dependency-Upgrade Addon
Safely bring a repo's dependencies up to date with a batched, validated, revertible workflow. This is the methodology's third opt-in addon — it is never required for a repo to be AI-first.
The rule that overrides everything: REASON about the package manager, then upgrade
The legacy version of this workflow assumed npm. It does not. The first job is to detect the repo's actual package manager from the manifest and lockfile that exist (see
SPEC.md§2 andtemplates/ecosystems.md), then drive that manager's real upgrade and install commands. Never runncu/pnpmin a Go, Rust, Python, Ruby, or PHP repo. Never assume a lockfile you have not seen.
Read these first (all relative inside the skill)
SPEC.md— the normative (RFC-2119) contract: detection, semver classification, batched-upgrade rule, validate-after-each-batch gate, revert-on-failure rule, reconcile-don't-clobber, validation step.templates/ecosystems.md— the per-ecosystem reasoning table: how to detect each manager and its real detect / classify / upgrade / install / lockfile commands. Match the row for the detected stack as a checklist, then verify against the real repo — detected reality wins.templates/upgrade-report.md— the report shape to summarize what was upgraded, skipped, reverted, and validated.templates/lib-upgrade-command.md— the/lib-upgradedelegator this addon installs into the target repo's.agents/commands/only when accepted.../README.md— the addon mechanism (opt-in, reconcile-don't-clobber, contract).
When this runs
- From
onboardPhase 7b — after the core AI-first scaffolding,onboardoffers this addon; if accepted it reads this SKILL and runs the flow below. - Directly —
/deepworkplan-addon-dependency-upgradeon an already-onboarded repo to upgrade dependencies, or via the installed/lib-upgradedelegator.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 131 lines · 152 tokens per session scan A a62bd384929a
deepworkplan-addon-dependency-upgrade is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 152 tokens to every session and 1,978 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…