Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/navikt/copilotnpx agentmods add skills/navikt/copilot/dependency-upgradeWrote 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/navikt/copilot/dependency-upgrade)<a href="https://agentmods.dev/skills/navikt/copilot/dependency-upgrade"><img src="https://agentmods.dev/badge/skills/navikt/copilot/dependency-upgrade/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/navikt/copilot/dependency-upgrade"><img src="https://agentmods.dev/badge/skills/navikt/copilot/dependency-upgrade.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.00076 | $0.02835 |
| Opus 5.5 | $0.00030 | $0.01134 |
| Sonnet 5.5 | $0.00015 | $0.00567 |
| Haiku 4.5 | $0.00008 | $0.00283 |
Grade A, and why
dependency-upgrade scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sfI "https://repo1.maven.org/maven2/<group-path>/<artifact>/<version>/<artifact>-<version>.pom" >/dev/null How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency upgrade
A recipe for upgrading a repo's direct dependencies that a small local model can
follow without inventing versions. It is built from what went right and wrong in
the nais/examples runs (navikt/mlx-workspace reports/2026-10-14-nais-examples-upgrade
and reports/2026-10-15-recipe-ab): lockfile-backed dependency bumps with tests
went green across Go, npm, Gradle and .NET, while unguarded runs invented tool
pins, image tags and CI versions, rewrote lockfiles with the wrong package
manager major, and bumped Postgres across majors.
The rule behind every step: only change what something in the repo will check.
When to Use
- "Upgrade the dependencies", "bump everything", "update npm packages"
- A Dependabot or Renovate backlog you want to clear in one pass
When NOT to Use
- Framework migrations that require code changes (Spring Boot 3→4, Jackson 2→3): use the dedicated migration skill
- A project with no lockfile or no test command: report that it has no lockfile/tests and skip it
1. Find each project and its ecosystem
List every project directory (a monorepo has several). Skip any project directory that lacks either a lockfile or a build/test command, and list it as skipped in the report. For each eligible project, record:
| Ecosystem | Lockfile | Upgrade command | Verify |
|---|---|---|---|
| Go | go.sum |
list direct updates with go list -m -u -f '{{if and (not .Indirect) .Update}}{{.Path}}@{{.Update.Version}}{{end}}' all, then go get <module>@<version> && go mod tidy (without -u, so only required transitive dependencies move) |
go build ./... && go test ./... |
| npm/pnpm/yarn | package-lock.json / pnpm-lock.yaml / yarn.lock |
the repo's pinned manager: npm update, pnpm update, or for Yarn an explicit verified same-major target (yarn upgrade <pkg>@<version> on Yarn 1, yarn up <pkg>@<version> on Yarn Berry); majors one package at a time |
<pm> run build (if defined) and <pm> test |
| Gradle | gradle/libs.versions.toml or gradle.lockfile |
edit the catalog / build file versions after step 4 lookup; if gradle.lockfile or dependency-locks/ is present, run ./gradlew dependencies --write-locks before verifying |
./gradlew build |
| .NET | packages.lock.json |
dotnet list package --outdated, then dotnet add package <id> --version <v> |
dotnet build && dotnet test |
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.
- yesterday First seen · 134 lines · 76 tokens per session scan A 081b353b632b
dependency-upgrade is a skill published in the GitHub repository navikt/copilot (55 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 2,835 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-16.
Other skills, from other repositories
press-clip
Turn a live article URL into a press clip that looks like the real coverage — the publication's own logo, fonts, photos and layout kept intact, the ads and clutter removed, and (for a roundup) just the client's section. Renders to PDF. You inspect each site and tailor the removal; the bundled script carries no…
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
prompt-proximity-architecture
Turn an approved measurement charter, ICPs, and buyer jobs into a budget-aware prompt coverage blueprint across proximity bands, aided status, information acts, journey states, roles, locales, evidence grades, partitions, and measurement lanes. Use before prompt wording to define required, optional, and prohibited…
coverage-tracker-setup
Set up a lightweight Google Alerts-style coverage tracker for any number of keywords. Creates a tracker config with each keyword and what it actually means, then hands recurrence to the user's agent harness.
prompt-set-qa
Gate a prompt universe for schema and provenance completeness, target or campaign contamination, evidence entailment, naturalness, one-concept clarity, architecture consistency, aided status, answer leakage, and semantic duplicates. Use after realistic prompt generation and before human panel selection.
realistic-prompt-generation
Generate natural, controlled prompt variants from a target-blind design brief and prompt architecture while preserving approved jobs, acts, journeys, constraints, roles, locales, proximity bands, and evidence language. Use after architecture design and before contamination or semantic QA.