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 commands/sugarfreebytes/aidevtools/update-ai-versionsgit clone --depth 1 https://github.com/sugarfreebytes/aidevtoolsWrote 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/commands/sugarfreebytes/aidevtools/update-ai-versions)<a href="https://agentmods.dev/commands/sugarfreebytes/aidevtools/update-ai-versions"><img src="https://agentmods.dev/badge/commands/sugarfreebytes/aidevtools/update-ai-versions.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.00024 | $0.00648 |
| Opus 5 | $0.00012 | $0.00324 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
update-ai-versions 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Edit, Bash(npm view *), Bash(curl *), WebFetch, WebSearch How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update AI tool versions in the Dockerfile
Your job is to refresh the pinned versions for the AI coding assistants in Dockerfile to whatever is current upstream right now, then edit the Dockerfile in place.
Steps
-
Read
Dockerfileand extract the current values for everyARG *_VERSIONline whose tool is an AI assistant. Today that means:CLAUDE_VERSION— Claude Code CLI, installed viahttps://claude.ai/install.shCODEX_VERSION— npm package@openai/codexGEMINI_VERSION— npm package@google/gemini-cli
If new
ARG *_VERSIONlines have been added for other AI assistants (e.g. opencode, cursor, copilot), include them too. Skip non-AI versions (Java, Node, Python, Go, Deno, NVM). -
Look up the latest version of each tool. Prefer the authoritative source per tool:
- npm packages →
npm view <package> version(fast, no auth needed). Both@openai/codexand@google/gemini-cliare on npm. - Claude Code CLI → fetch
https://claude.ai/install.shand read the version it defaults to, or check the GitHub releases page foranthropics/claude-code. Pick whichever returns a clean version string. - For any other tool: use
npm viewif it's an npm package, otherwise WebFetch the project's releases page or WebSearch for " latest version".
Run these lookups in parallel where possible.
- npm packages →
-
Compare each fetched version to what's currently in the Dockerfile. Build a short table of
tool: current → latestand print it so the user can see what's about to change. -
Edit the Dockerfile: for each tool whose version actually changed, update the corresponding
ARG <TOOL>_VERSION=<value>line. Use the Edit tool, one edit per line. Do not touch lines for tools that are already up to date. Do not reformat or reorder anything. -
Report the final result: list each tool with
unchangedorold → new. Do not commit — leave the diff staged for the user to review.
Notes
- The Claude install script convention is
bash -s <version>with a bare semver (novprefix). Match the existing format in the Dockerfile for each tool (some have avprefix, some don't — preserve whatever style is already there). - If a lookup fails (network error, package renamed, etc.), report it and skip that tool rather than guessing a version.
- Do not invent new ARG lines or install new tools — this command only refreshes existing pins.
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.
- 4d ago First seen · 37 lines · 24 tokens per session scan A 00cf7868d41b
update-ai-versions is a command published in the GitHub repository sugarfreebytes/aidevtools (1 stars, last pushed 26d ago), licensed MIT. It adds 24 tokens to every session and 648 once invoked, about $0.0001 per session on Opus 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-08-31.
Other commands, from other repositories
models
List available models for all AI agents.
status
Quick health check of all AI agents.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
om-peer-scan
Deep scan a peer's GitHub PRs for performance review preparation. Produces a structured analysis saved to perf/evidence/.
om-dump
Freeform capture mode. Dump anything — conversations, decisions, incidents, wins, thoughts — and I'll route it all to the right notes with proper templates, frontmatter, and wikilinks.
session-stop
Stop recording and save this agent session to the project ledger.