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 joshukraine/dotfiles --skill update-depsgit clone --depth 1 https://github.com/joshukraine/dotfilesWrote 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/joshukraine/dotfiles/update-deps)<a href="https://agentmods.dev/skills/joshukraine/dotfiles/update-deps"><img src="https://agentmods.dev/badge/skills/joshukraine/dotfiles/update-deps.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.1 | $0.00028 | $0.02175 |
| Opus 5 | $0.00014 | $0.01087 |
| Sonnet 5 | $0.00006 | $0.00435 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
update-deps 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 7d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Dependencies
Update project dependencies safely: reconcile open Dependabot PRs into one unified change, run the project's security audit, validate boot-affecting changes against the real CI environment, and open a single PR — instead of stopping at local commits.
This skill is framework-agnostic. It detects the project's package manager, test/lint commands, audit suite, and CI workflow rather than assuming a stack.
Command Options
--dry-run: Show what would be updated without making changes--major: Include major version updates (default: minor/patch only)--package <name>: Update specific package only--skip-tests: Skip running tests between updates
Workflow at a glance
Detect → Reconcile Dependabot → Update → Audit → Validate on real CI → Open PR → Verify auto-close
Each stage feeds the next. Don't skip the audit or the real-CI validation for boot-affecting changes — those are the two stages that catch what local tests can't.
Your task
1. Detect the environment (do not hardcode)
Detect both the package manager and the project's real entry points. The runners below are common defaults, not assumptions — always confirm against what the repo actually uses.
- Package manager:
package.json(npm/yarn/pnpm) — check the lockfile to disambiguateGemfile(bundler)requirements.txt/pyproject.toml(pip/poetry/uv)Cargo.toml(cargo)go.mod(go modules)
- Test/lint/CI entry points — prefer a single project gate over assumed runners:
- A wrapper script like
bin/ci,bin/test,script/test, or aMakefile/Justfiletarget is the canonical gate — use it if present. - Otherwise detect the real tools: Minitest vs RSpec, StandardRB vs RuboCop, Herb, Biome vs ESLint, Prettier,
tsc,mypy, etc. - Detect the CI workflow itself: list
.github/workflows/*.ymland identify the workflow that runs on the default branch and the jobs it contains.
- A wrapper script like
- Audit suite (see step 4) — detect, don't assume.
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.
- 7d ago First seen · 201 lines · 28 tokens per session scan A 6f50a136d9fa
update-deps is a skill published in the GitHub repository joshukraine/dotfiles (422 stars, last pushed 25d ago), licensed MIT. It adds 28 tokens to every session and 2,175 once invoked, about $0.0001 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
cmux-rebuild
Manage the user's durable dev sessions — zellij sessions on remote hosts (bonbon, taffy) reached over mosh, plus the local host's (trifle) own detached zellij sessions, surfaced as cmux tabs via ssh::durable / zellij::resume. Load when the user wants to rebuild/resurrect lost cmux durable surfaces after a cmux restart…
cmux-fork-session
Fork the current agent session — Claude Code or pi — into a new cmux split pane (or tab): opens a split beside the caller, relaunches this session forked (claude --fork-session / pi --fork), titles it 'fork: ', and keeps that title. Use when the user asks to fork/duplicate/branch the current session into a new split…
ml-paper-writing
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
python-conventions
Python coding conventions, modern tooling, and project setup. Apply when writing or reviewing Python code, creating projects, writing scripts, or migrating from legacy tools. Covers uv, ruff, ty, type hints, code structure, async, testing, and project configuration.
review-pr
Review an existing GitHub PR — one verified single-pass read of the diff, inline P1–P3 findings, fixes for the P1/P2s pushed to the PR branch, scoped verification, resolved threads, a summary. Escalates to a two-reader second opinion only for large source changes. Use when asked to review and fix a PR, or to run the…
slidesync
Bidirectional sync between a Slidev markdown deck and Google Slides as native, editable objects (not images). Push markdown -> Slides, pull Slides -> markdown, and round-trip. Use when the user wants to author/version a Google Slides deck from markdown, replicate a deck's styling, or keep a .slidev.md in sync with a…