Borrowing it
Nothing to install: this file belongs to rigortype/rigor. 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/rigortype/rigor/master/.claude/skills/rigor-dependency-update/SKILL.mdgit clone --depth 1 https://github.com/rigortype/rigorWrote 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/rigortype/rigor/rigor-dependency-update)<a href="https://agentmods.dev/skills/rigortype/rigor/rigor-dependency-update"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-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/rigortype/rigor/rigor-dependency-update"><img src="https://agentmods.dev/badge/skills/rigortype/rigor/rigor-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.00058 | $0.03132 |
| Opus 5.5 | $0.00023 | $0.01253 |
| Sonnet 5.5 | $0.00012 | $0.00626 |
| Haiku 4.5 | $0.00006 | $0.00313 |
Grade C, and why
rigor-dependency-update scanned grade C 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 11d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf vendor/bundle How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update dependencies (two layers)
The project's dependencies live in two independent layers, and the first job is to keep them separate — a single "update the deps" request usually means both, but they are different kinds of change and belong in different commits so history stays legible.
- Bundled gems —
Gemfile.lock. The runtime-affecting layer: the analyzer's own dependencies (prism,rbs,language_server-protocol) plus dev tooling (rubocop,rspec,binpacker, …). Managed withbundle update. Every bump here also has to be mirrored into the Nix package's own lock (see "The Nix package lock"). - Nix Flake dev environment —
flake.lock. The development layer: the pinnednixpkgs-unstablerevision that provisions the dev shell (make, git base, bundix, the Ruby build inputs). Managed withnix flake update.
Do both by default, but each layer is a self-contained commit, so doing
one alone is fine. Work on a branch and open one PR carrying both
commits (the public-dev workflow — grouped changes go through a PR, not a
direct push to master).
Use bundle / nix commands; never hand-edit a lockfile.
Layer 1 — bundled gems (bundle update)
See what is available first, then update within the existing gemspec constraints:
nix develop --command bundle outdated
nix develop --command bundle update
bundle update re-resolves every gem to the latest version the
gemspec's existing ranges allow. This is a lockfile refresh only —
git diff Gemfile.lock should show version bumps and nothing structural.
Two judgment calls the resolver makes for you, worth confirming:
- A held-back major is not a blocker to chase. If
bundle outdatedlists a new major (e.g.diff-lcs 2.0) butbundle updatekeeps the old one, a transitive constraint is capping it (rspec pinsdiff-lcs < 2.0). That is correct — leave it. Pulling a major that the gemspec ranges forbid would require a gemspec range change, which is a deliberate decision outside this skill (edit the gemspec viabundle add, verify the new major, land it on its own).
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.
- 11d ago First seen · 265 lines · 58 tokens per session scan C 7d87b2073576
rigor-dependency-update is a skill published in the GitHub repository rigortype/rigor (107 stars, last pushed today), licensed MPL-2.0. It adds 58 tokens to every session and 3,132 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-26.
rigor-dependency-update compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| rigor-dependency-updaterigortype/rigor | Skill | 107 | today | MPL-2.0 | C | 58 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |