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 skills add d-o-hub/github-template-ai-agents --skill dependency-upgradesgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/dependency-upgrades)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/dependency-upgrades"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/dependency-upgrades/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/d-o-hub/github-template-ai-agents/dependency-upgrades"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/dependency-upgrades.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.00083 | $0.00600 |
| Opus 5.5 | $0.00033 | $0.00240 |
| Sonnet 5.5 | $0.00017 | $0.00120 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
dependency-upgrades 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 25d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Upgrades
Routine bumps and CVE-driven upgrades: one dependency per change, verified by CI, with a rollback path.
When to Use
- Bumping a package, action version, or base image
- Vulnerability alert (CVE, Dependabot, audit finding)
- Lockfile refresh or stale pins
Steps
- Scope one upgrade — one dependency per PR/branch so failures attribute cleanly. Group only provably-coupled pairs.
- Read the changelog — note breaking changes and migration notes before bumping, not after CI fails.
- Bump + lock — update the manifest and regenerate the lockfile with the project's canonical tool; never hand-edit lockfiles.
- Verify — full relevant test suite plus the quality gate; for security bumps, confirm the CVE is actually remediated (audit clean).
- Record rollback — pin the previous version in the PR body so revert is one commit.
Rules
- Never bump major versions together with unrelated changes.
- Never ignore a lockfile diff — read it; unexpected transitive churn is a signal, not noise.
- Never merge a security upgrade red (failing checks void the point).
- This repo's Dependabot groups all action minor/patch bumps into one PR
(
.github/dependabot.yml) and auto-merges via ADR-032 whenMAINTAINER_AUTOMATION=true; never let that bypass the verify step.
Rationalizations
| Rationalization | Reality |
|---|---|
| "It's just a patch bump, skip the tests" | Patch releases introduce regressions regularly; the suite is cheaper than the incident. |
| "Dependabot already tested it" | Bot CI covers the bot's matrix, not your integration paths; run your gates. |
Red Flags
- Major bump bundled with feature work
- Hand-edited lockfile
- CVE upgrade merged with failing checks
See Also
migration-refactoring— Framework and language migrationstest-runner— Execute tests after the bumpgit-github-workflow— Ship the upgrade end-to-end
References
evals/evals.json— upgrade cases incl. breaking-change negative
What ships with it
1 file 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.
- 25d ago First seen · 65 lines · 83 tokens per session scan A 204509debc5d
dependency-upgrades is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 600 once invoked, about $0.0003 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-09-28.
Other skills, from other repositories
supply-chain
Secure the software supply chain from source to running container. Covers Cosign keyless image signing (Sigstore/Rekor), SBOM generation and attestation (Syft), vulnerability scanning with severity gates (Trivy/Grype), SLSA Level 2 provenance, and Kyverno/OPA admission enforcement. All open-source, no license cost.…
trivy
Scan container images, filesystems, git repos, and existing SBOMs for CVEs, secrets, and license violations using Trivy. Covers local CLI, CI severity gates with SARIF upload, and continuous monitoring via Trivy Operator (Flux HelmRelease). Use when asked to "scan my image", "check for CVEs", "scan this repo for…
platform-skills
Use when troubleshooting, implementing, reviewing, or auditing platform infrastructure as a system — where Kubernetes, GitOps, CI/CD, and security concerns intersect. Provides structured diagnosis with blast radius, validation steps, and rollback plan for: Kubernetes, Flux CD, Argo CD, Terraform, GitHub Actions…
docker-build-deploy
Use when containerizing a Node.js app and setting up GitHub Actions CI/CD to build, push to GHCR, and deploy via SSH. Multi-stage build, non-root user, caching.
devops-commander
Activates the DevOps-Commander agent for infrastructure, CI/CD, and cloud operations. Use when you need GitHub Actions or GitLab CI pipeline design, Dockerfile and docker-compose configuration, Kubernetes deployment manifests, Terraform/Pulumi infrastructure as code, Prometheus + Grafana monitoring setup, or incident…
deploy-agent
You are the Deploy agent for this project. You own CI/CD, infrastructure-as-code, Docker, deploy scripts, and environment configuration.