Borrowing it
Nothing to install: this file belongs to shino369/claude-code-personal-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shino369/claude-code-personal-workspace/main/.claude/skills/dependency-update/SKILL.mdgit clone --depth 1 https://github.com/shino369/claude-code-personal-workspaceWrote 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/shino369/claude-code-personal-workspace/dependency-update)<a href="https://agentmods.dev/skills/shino369/claude-code-personal-workspace/dependency-update"><img src="https://agentmods.dev/badge/skills/shino369/claude-code-personal-workspace/dependency-update/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/skills/shino369/claude-code-personal-workspace/dependency-update"><img src="https://agentmods.dev/badge/skills/shino369/claude-code-personal-workspace/dependency-update.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.00105 | $0.02265 |
| Opus 5.5 | $0.00042 | $0.00906 |
| Sonnet 5.5 | $0.00021 | $0.00453 |
| Haiku 4.5 | $0.00011 | $0.00227 |
Grade A, and why
dependency-update 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 10d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Update
Dependabot-style dependency maintenance for any pnpm workspace. Covers three tasks — pick by intent:
| The user wants to… | Workflow | Detail |
|---|---|---|
| Update / upgrade packages, check outdated, check majors | 1. Packages | references/package-updates.md |
| Bump Node / pnpm version | 2. Runtime | references/runtime-versions.md |
| Review / verify a Dependabot PR, comment a verdict | 3. PR review | references/dependabot-pr-review.md |
Routing: this skill handles version currency. For a vulnerability / CVE / pnpm audit
finding, use the security-update skill instead — it owns the audit → overrides flow.
Discover the project first — never assume
This skill is settings-agnostic: discover how this project is configured before acting. The analyzer and the verification pipeline both adapt to what you find.
- Where versions live — read
pnpm-workspace.yaml. If it definescatalog:/catalogs:, versions live there andpackage.jsonreferences them ascatalog:<name>. Otherwise versions are plain ranges inpackage.json.analyze_deps.mjshandles both automatically. - Safety policy the project enforces — check
pnpm-workspace.yaml(and.npmrc) for any of:minimumReleaseAge(+minimumReleaseAgeExclude) — a release cooldown; if set,pnpm installrefuses versions younger than it. The analyzer reads and reports this; don't hardcode a number.strictPeerDependencies— iftrue, install hard-fails on peer conflicts.engineStrict+engines— iftrue, install fails below the required Node/pnpm.packageManagerStrict(pnpm ≤11) — iftrue, pnpm refuses to run whenpackage.json'spackageManagerfield does not match the running version. pnpm 12 enforces the field directly.overrides— pins for transitive deps (usually security; leave to the security-update flow).
- Verification scripts — read
package.jsonscriptsand map the pipeline to whatever names exist (typecheck/tsc/compile,test,lint,format,build). - Automation + repo —
.github/dependabot.ymlorrenovate.json(grouping, ignored majors, rebase strategy);gh repo view --json nameWithOwnerfor the current repo. - Runtime version files (task 2) — which of
.nvmrc,.node-version,.tool-versions,mise.toml,pnpm-workspace.yaml(nodeVersion),package.json(engines,packageManager,volta),Dockerfile*, or CI workflows this project actually uses.
What ships with it
5 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.
- 10d ago First seen · 150 lines · 105 tokens per session scan A 21d4a2b96f5d
dependency-update is a skill published in the GitHub repository shino369/claude-code-personal-workspace (3 stars, last pushed 11d ago), licensed ISC. It adds 105 tokens to every session and 2,265 once invoked, about $0.0004 per session on Opus 5.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-10-18.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.