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 agentmods add skills/fmind/dot/upgrade-toolsnpx skills add fmind/dot --skill upgrade-toolsgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/upgrade-tools)<a href="https://agentmods.dev/skills/fmind/dot/upgrade-tools"><img src="https://agentmods.dev/badge/skills/fmind/dot/upgrade-tools.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 | $0.00036 | $0.00778 |
| Opus 5 | $0.00018 | $0.00389 |
| Sonnet 5 | $0.00007 | $0.00156 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
upgrade-tools 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 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.
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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Tools
Bump every pinned tool and dependency to its latest stable version, one ecosystem at a time, validating after each so a bad bump is caught immediately; the per-manifest commands live in the playbook and mise owns the tool pins.
Workflow
- Baseline:
mise run checkandmise run testmust be green before the first bump so regressions are attributable. - mise first: it provisions the toolchain every later step runs; bump and re-lock the pins per mise, then validate.
- Language dependencies next (Go, Python, Node, Rust) decide whether the new toolchain compiles the project; follow the playbook per manifest and validate after each.
- Infrastructure and images after that (OpenTofu providers, container base images), which consume the language artifacts.
- CI and formatter config last (GitHub Actions, dprint), the outermost layer and the least likely to cascade.
- Stop at the first failing ecosystem and fix it before continuing; bumping the rest on top of a broken one turns a short upgrade into an afternoon of bisecting.
- Run the hooks once at the end:
lefthook run pre-commit --all-filesandlefthook run pre-push --all-files. - Commit per ecosystem:
chore(deps): upgrade <ecosystem> to latestwith its lockfile, per conventional-commit.
Gotchas
- Latest stable only: no RCs, betas, or pre-releases; tools deliberately range-pinned pre-1.0 stay in their range.
- Lockfiles are the record: commit
mise.lock,go.sum,uv.lock,pnpm-lock.yaml,.terraform.lock.hcl; the manifest says "latest", the lockfile says which. - Majors are separate changes:
go get -uanduv lock --upgradestay within declared majors; a major bump gets its own reviewed change. - Held-back pins: a pin kept below latest carries a comment saying why (a parser ABI, a broken upstream asset); re-pin it deliberately instead of letting a bump carry it forward silently.
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 · 40 lines · 36 tokens per session scan A a2b6900c4b5e
upgrade-tools is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 778 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.